Triple
T27903565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana–Maharashtra border |
E705705
|
entity |
| Predicate | hasAdjacentDistrictInMaharashtra |
P168028
|
FINISHED |
| Object | Gadchiroli district |
—
|
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: Gadchiroli district | Statement: [Telangana–Maharashtra border, hasAdjacentDistrictInMaharashtra, Gadchiroli district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentDistrictInMaharashtra Context triple: [Telangana–Maharashtra border, hasAdjacentDistrictInMaharashtra, Gadchiroli district]
-
A.
hasRelatedDistrict
Indicates that one entity is associated with, linked to, or falls within the scope of a particular district.
-
B.
hasNeighbouringDivision
chosen
Indicates that one division is directly adjacent to and shares a boundary with another division.
-
C.
hasDistrictHealthBoard
Indicates that an entity is served, governed, or overseen by a specific district health board.
-
D.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
E.
hasAdjacentArrondissement
Indicates that one arrondissement is directly next to or shares a boundary with another arrondissement.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 6:43 p.m.