Triple
T2026460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crimean Tatar flag |
E44417
|
entity |
| Predicate | emblemSymbolism |
P34702
|
FINISHED |
| Object | Crimean Tatar ruling lineage |
—
|
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: Crimean Tatar ruling lineage | Statement: [Crimean Tatar flag, emblemSymbolism, Crimean Tatar ruling lineage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemSymbolism Context triple: [Crimean Tatar flag, emblemSymbolism, Crimean Tatar ruling lineage]
-
A.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
C.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
D.
definesEmblem
Indicates that one entity specifies or establishes the official emblem associated with another entity.
-
E.
protectiveEmblemName
Indicates that a given name is the designated title or label of a protective emblem associated with an entity or context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.