Triple
T23681652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gird region |
E585038
|
entity |
| Predicate | politicalRegionOf |
P64798
|
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: [Gird region, politicalRegionOf, Madhya Pradesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalRegionOf Context triple: [Gird region, politicalRegionOf, Madhya Pradesh]
-
A.
politicalRegionType
Indicates the classification of a political region according to its governmental or administrative type (e.g., state, province, municipality).
-
B.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
C.
politicalRegionRepresented
Indicates that one entity serves as the official political representative or governing body for a specified geographic or administrative region.
-
D.
populationRegion
Indicates that a specified population is located within or associated with a particular geographic region.
-
E.
geopoliticalRegion
Indicates a relationship where an entity is a defined political or administrative geographic area, such as a country, state, province, or similar region.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f835ec8190a7bdcfa48ad79cd5 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:51 p.m.