Triple
T34688516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanjak of Genç |
E890816
|
entity |
| Predicate | hasLanguageInAdministration |
P9278
|
FINISHED |
| Object | Ottoman Turkish |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Ottoman Turkish | Statement: [Sanjak of Genç, hasLanguageInAdministration, Ottoman Turkish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageInAdministration Context triple: [Sanjak of Genç, hasLanguageInAdministration, Ottoman Turkish]
-
A.
usesLanguageForAdministration
Indicates that an entity employs a particular language as the official medium for its administrative or governmental functions.
-
B.
languageOfCurrentAdministration
Indicates the language currently used by the governing or administrative authority in charge.
-
C.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
hasLanguageOn
chosen
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
E.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 1, 2026, 2:05 a.m.