Triple
T23752329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goverdhan |
E587002
|
entity |
| Predicate | partOfElectoralState |
P19338
|
FINISHED |
| Object | Uttar Pradesh |
—
|
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: Uttar Pradesh | Statement: [Goverdhan, partOfElectoralState, Uttar Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfElectoralState Context triple: [Goverdhan, partOfElectoralState, Uttar Pradesh]
-
A.
locatedInStateElectorate
Indicates that one entity is geographically situated within the boundaries of a particular state electoral district.
-
B.
electorateState
chosen
Indicates the state or region in which a given electorate (voting district or constituency) is located or to which it belongs.
-
C.
representedState
Indicates that one entity serves as a representation or depiction of the state or condition of another entity.
-
D.
seatOfElector
Indicates the location or jurisdiction that serves as the official base or constituency of a given elector.
-
E.
legislativeDistrictOf
Indicates that a specified geographic or political area is the legislative district in which a given entity (such as a person, organization, or location) is situated or represented.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc289e08190a8036bb16dd0220a |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.