Triple
T2026466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean Tatar flag |
E44417
|
entity |
| Predicate | writingDirectionOfName |
P2264
|
FINISHED |
| Object | left-to-right |
—
|
LITERAL FINISHED |
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: left-to-right | Statement: [Crimean Tatar flag, writingDirectionOfName, left-to-right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingDirectionOfName Context triple: [Crimean Tatar flag, writingDirectionOfName, left-to-right]
-
A.
hasWritingDirection
chosen
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
B.
translationDirection
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
C.
languageFamilyWritten
Indicates that one language family is represented or recorded in a particular written form or script.
-
D.
nameInLatinAlphabet
Indicates that an entity’s name is written or represented using the Latin alphabet.
-
E.
writingSystemStandardized
Indicates that a writing system has been formally codified and regulated according to an accepted standard or set of rules.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.