Triple
T23694063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jobat |
E585384
|
entity |
| Predicate | isStateConstituencyOf |
P84299
|
FINISHED |
| Object | Madhya 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: Madhya Pradesh | Statement: [Jobat, isStateConstituencyOf, Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStateConstituencyOf Context triple: [Jobat, isStateConstituencyOf, Madhya Pradesh]
-
A.
hasStateOrDistrict
chosen
Indicates that an entity is associated with, located in, or belongs to a particular state or district.
-
B.
borderingConstituencyState
Indicates that a constituency shares a common boundary with a particular state.
-
C.
hasLegislativeState
Indicates that an entity is associated with, governed by, or falls under the jurisdiction of a particular legislative state or lawmaking authority.
-
D.
stateOfCongressionalDistrict
Indicates the relationship where a specific congressional district is located within or belongs to a particular U.S. state.
-
E.
isBoroughConstituency
Indicates that a parliamentary or electoral constituency is classified specifically as a borough constituency, as opposed to other constituency types.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c47b80819083f31dbd5443343e |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.