Triple
T25259671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian flag laws |
E633268
|
entity |
| Predicate | supersededInstrument |
P101
|
FINISHED |
| Object | Flag Code of India, 1950 |
—
|
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: Flag Code of India, 1950 | Statement: [Indian flag laws, supersededInstrument, Flag Code of India, 1950]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededInstrument Context triple: [Indian flag laws, supersededInstrument, Flag Code of India, 1950]
-
A.
wasSupersededBy
chosen
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
upgradedInstrument
Indicates that one instrument has been improved or replaced by another, more advanced instrument.
-
C.
supersededSpecificationIn
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
D.
supersededAward
Indicates that one award has been replaced or made obsolete by another award.
-
E.
affectedInstrument
Indicates that an instrument or tool is impacted, altered, or influenced as a result of an action or event.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 1:13 p.m.