Triple
T34130815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daltonganj Assembly constituency |
E875418
|
entity |
| Predicate | administrativeStateFormationYear |
P195005
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Daltonganj Assembly constituency, administrativeStateFormationYear, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStateFormationYear Context triple: [Daltonganj Assembly constituency, administrativeStateFormationYear, 2000]
-
A.
hasYearOfEstablishment
Indicates the specific year in which an entity was founded, created, or formally established.
-
B.
incorporationYear
Indicates the calendar year in which an organization or entity was formally incorporated or legally established.
-
C.
hasAllegedFormationYear
Indicates that an entity is associated with a claimed or reported year in which it was formed, though this year may be uncertain or disputed.
-
D.
underlyingCompanyFormationYear
Indicates the calendar year in which the referenced underlying company was originally formed or established.
-
E.
districtFormationYear
Indicates the year in which a district was officially established or formed.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: May 1, 2026, 1:53 a.m.