Triple
T38018873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khizarsarai |
E948567
|
entity |
| Predicate | locatedInCensusState |
P96807
|
FINISHED |
| Object | Bihar |
E60958
|
NE 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: Bihar | Statement: [Khizarsarai, locatedInCensusState, Bihar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCensusState Context triple: [Khizarsarai, locatedInCensusState, Bihar]
-
A.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
locatedInFederalEntity
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
C.
housedInState
Indicates that an entity is located or situated within the boundaries of a particular state.
-
D.
locatedInFormerState
Indicates that an entity is or was geographically situated within the boundaries of a political state that no longer exists in its former form.
-
E.
locatedInUnion
Indicates that an entity is situated within or is a member of a specific union or collective grouping.
- F. None of above.
Provenance (4 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_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41711136d88190a9b7eb4ad23dd688 |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.