Triple
T22277467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratlam Lok Sabha constituency |
E550643
|
entity |
| Predicate | stateNumbering |
P138276
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Ratlam Lok Sabha constituency, stateNumbering, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateNumbering Context triple: [Ratlam Lok Sabha constituency, stateNumbering, 23]
-
A.
statePosition
Indicates the spatial or situational position or status of an entity within a defined context or system.
-
B.
isNumberedWithinState
chosen
Indicates that an entity has an assigned number that is unique or valid only within the context or boundaries of a particular state.
-
C.
congressionalNumberingState
Indicates the state associated with a particular numbering or designation of a congressional body or district.
-
D.
legalNumbering
Indicates that an entity has an officially assigned legal or regulatory identification number.
-
E.
regionNumber
Indicates that an entity is assigned to or associated with a specific numbered region within a larger spatial or organizational division.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14ea8a6688190bcd168670420ec59 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.