Triple
T11334967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States of India |
E268448
|
entity |
| Predicate | previousNumberOfStatesBefore2019 |
P24416
|
FINISHED |
| Object | 29 |
—
|
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: 29 | Statement: [States of India, previousNumberOfStatesBefore2019, 29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNumberOfStatesBefore2019 Context triple: [States of India, previousNumberOfStatesBefore2019, 29]
-
A.
statusBefore2022
Indicates that an entity’s status or condition is defined as it existed prior to the year 2022.
-
B.
statusAfter2019
Indicates the condition or state of an entity specifically in the period following the year 2019.
-
C.
previousNumberOfConstituents
chosen
Indicates the number of constituents an entity had at an earlier point in time, before its current state.
-
D.
formerStateOrderOf
Indicates that one state previously held authority or jurisdiction over another state in an earlier political or administrative order.
-
E.
formerState
Indicates that an entity previously held the status or condition of a particular state but no longer does so.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9ff62c88190a089dd84e2ac1d17 |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.