Triple
T1106030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion Capital of Ashoka |
E25488
|
entity |
| Predicate | adoptionDateAsNationalEmblem |
P3399
|
FINISHED |
| Object | 26 January 1950 |
—
|
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: 26 January 1950 | Statement: [Lion Capital of Ashoka, adoptionDateAsNationalEmblem, 26 January 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptionDateAsNationalEmblem Context triple: [Lion Capital of Ashoka, adoptionDateAsNationalEmblem, 26 January 1950]
-
A.
adoptedAsEmblemBy
Indicates that something has been officially chosen and used as a symbolic emblem by a particular entity or group.
-
B.
hasNationalSymbol
Indicates that an entity possesses or is associated with an officially recognized national symbol of a country or nation.
-
C.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
D.
adoptedAsNationalAnthemYear
Indicates the year in which something was officially adopted as a national anthem.
-
E.
adoptedAsNationalAnthemInYear
Indicates that a song or musical composition was officially adopted as a country's national anthem in a specified year.
- 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e339f88190afc027216e95d2f7 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.