Triple
T34717700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasaram (Bihar Assembly constituency) |
E1000823
|
entity |
| Predicate | stateCapitalOfJurisdiction |
P71239
|
FINISHED |
| Object | Patna |
—
|
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: Patna | Statement: [Sasaram (Bihar Assembly constituency), stateCapitalOfJurisdiction, Patna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalOfJurisdiction Context triple: [Sasaram (Bihar Assembly constituency), stateCapitalOfJurisdiction, Patna]
-
A.
governingStateCapital
Indicates that a state serves as the governing political authority over the specified capital city.
-
B.
capitalOfMajorState
Indicates that one location serves as the primary capital city of a major state or significant administrative region.
-
C.
stateCapitalFunction
Indicates that one location serves as the official capital city and primary seat of government for a given state.
-
D.
governsCapital
Indicates that a political authority or administrative body exercises governing control over a capital city.
-
E.
capitalCityOfAssociatedState
chosen
Indicates that a city serves as the capital of the state with which another entity is associated.
- 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_69f76dad3f108190a280fd0a2f4ee89a |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: May 3, 2026, 3:59 p.m.