Triple
T38019575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaya Lok Sabha constituency |
E948590
|
entity |
| Predicate | stateAfterDelimitation |
P160185
|
FINISHED |
| Object | Bihar |
—
|
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: Bihar | Statement: [Gaya Lok Sabha constituency, stateAfterDelimitation, Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateAfterDelimitation Context triple: [Gaya Lok Sabha constituency, stateAfterDelimitation, Bihar]
-
A.
postDelimitation
chosen
Indicates that the related action, status, or condition occurs after a specified boundary, cutoff point, or delimiting event.
-
B.
currentDelimitationFrom
Indicates that one entity currently defines or establishes the boundary or extent of another entity.
-
C.
lastDelimitationOrder
Indicates the most recent official boundary-setting or redistricting order that defines or updates the limits of an area or jurisdiction.
-
D.
separatesAt
Indicates that one entity divides or splits another entity into distinct parts at a specific point, boundary, or location.
-
E.
stageAfter
Indicates that one stage occurs later in sequence or order than another specified stage.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 3, 2026, 4:20 p.m.