Triple
T29351045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Kurdish |
E744313
|
entity |
| Predicate | standardVarietyIn |
P5199
|
FINISHED |
| Object | Turkey |
—
|
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: Turkey | Statement: [Northern Kurdish, standardVarietyIn, Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardVarietyIn Context triple: [Northern Kurdish, standardVarietyIn, Turkey]
-
A.
standardVarietyBasedIn
chosen
Indicates that a standard or reference variety (such as a language or dialect) is primarily established, recognized, or centered in a particular location or region.
-
B.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
D.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
E.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
- 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_69f0a79a2d748190bc30abd469298b37 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 2:06 p.m.