Triple
T23467375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odisha Legislative Assembly constituencies |
E569131
|
entity |
| Predicate | electoralBoundaryType |
P152394
|
FINISHED |
| Object | territorial |
—
|
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: territorial | Statement: [Odisha Legislative Assembly constituencies, electoralBoundaryType, territorial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralBoundaryType Context triple: [Odisha Legislative Assembly constituencies, electoralBoundaryType, territorial]
-
A.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
B.
electoralBoundaryAuthority
Indicates the authority or body responsible for defining, managing, or overseeing electoral boundaries for a given area.
-
C.
constituencyType
Indicates the specific kind or category of electoral or representative district to which an entity belongs or refers.
-
D.
partOfElectoralDistrictType
Indicates that one entity is a component or subdivision of a specified type of electoral district.
-
E.
borderingConstituency
Indicates that one political constituency shares a common boundary with another constituency.
- F. None of above. chosen
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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6fc35c48190a67614fb4170f15b |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:54 p.m.