Triple
T2089319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haridwar |
E32629
|
entity |
| Predicate | stateFormationContext |
P19781
|
FINISHED |
| Object | became part of Uttarakhand in 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: became part of Uttarakhand in 2000 | Statement: [Haridwar, stateFormationContext, became part of Uttarakhand in 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateFormationContext Context triple: [Haridwar, stateFormationContext, became part of Uttarakhand in 2000]
-
A.
stateBeforeFormation
Indicates a relationship where one state or condition existed prior to the formation or creation of another entity or state.
-
B.
statehoodContext
chosen
Indicates the contextual circumstances, conditions, or framework under which an entity’s status as a state (or its statehood) is defined, recognized, or discussed.
-
C.
stateRock
Indicates that an entity is in a solid, rock-like physical state or condition.
-
D.
statesBoundOfForm
Indicates that one state or condition serves as a boundary or limiting form for another.
-
E.
governmentFormOfRuledState
Indicates the type of governmental system or structure by which a particular state or territory is ruled.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba730a5c8190a85be72149574d79 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b4356881909217c42ccb8bb1ed |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.