Triple
T1569565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil Nadu |
E33506
|
entity |
| Predicate | hasOfficialEmblem |
P18440
|
FINISHED |
| Object | Emblem of Tamil Nadu |
—
|
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: Emblem of Tamil Nadu | Statement: [Tamil Nadu, hasOfficialEmblem, Emblem of Tamil Nadu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialEmblem Context triple: [Tamil Nadu, hasOfficialEmblem, Emblem of Tamil Nadu]
-
A.
emblemStatus
Indicates the current state or condition of an emblem, such as whether it is active, valid, displayed, or in use.
-
B.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
C.
hasOfficialInsigniaLocation
Indicates the specific place where an entity’s official insignia is physically located or displayed.
-
D.
adoptedAsEmblemBy
chosen
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
-
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.
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_69a885f11b048190935025a035302715 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.