Triple
T20081548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhind Assembly constituency |
E500012
|
entity |
| Predicate | isGeographicallyLocatedIn |
P40
|
FINISHED |
| Object | northern Madhya Pradesh |
—
|
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: northern Madhya Pradesh | Statement: [Bhind Assembly constituency, isGeographicallyLocatedIn, northern Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeographicallyLocatedIn Context triple: [Bhind Assembly constituency, isGeographicallyLocatedIn, northern Madhya Pradesh]
-
A.
isLocatedOn
Indicates that one entity exists at or is situated upon the surface or area of another entity.
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
D.
isGeographicalEntity
Indicates that something exists as a distinct geographic feature, area, or place within physical space.
-
E.
placeFoundedLocatedIn
Indicates that the location where something was founded is situated within a specified place.
- 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e665588a9c8190886b693b13a215a8 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:41 p.m.