Triple
T30789398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melghat (Vidhan Sabha constituency) |
E784049
|
entity |
| Predicate | administrativeHeadquarterNearby |
P44325
|
FINISHED |
| Object | Amravati |
—
|
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: Amravati | Statement: [Melghat (Vidhan Sabha constituency), administrativeHeadquarterNearby, Amravati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeHeadquarterNearby Context triple: [Melghat (Vidhan Sabha constituency), administrativeHeadquarterNearby, Amravati]
-
A.
nearHeadquartersOf
chosen
Indicates that one entity is located geographically close to the headquarters of another entity.
-
B.
administrativeCentreNearby
Indicates that an administrative centre is located close to the referenced entity in geographic or spatial terms.
-
C.
hasNearbyHeadquarters
Indicates that the headquarters of two entities are located geographically close to each other.
-
D.
administrativeHeadquarter
Indicates the location that serves as the main administrative center or headquarters for an organization or governing body.
-
E.
nearestDistrictHeadquarters
Indicates that one location is the closest district headquarters to another 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: April 29, 2026, 8:41 p.m.