Triple
T27903559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana–Maharashtra border |
E705705
|
entity |
| Predicate | hasAdjacentDistrictInTelangana |
P168028
|
FINISHED |
| Object | Adilabad 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: Adilabad district | Statement: [Telangana–Maharashtra border, hasAdjacentDistrictInTelangana, Adilabad district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentDistrictInTelangana Context triple: [Telangana–Maharashtra border, hasAdjacentDistrictInTelangana, Adilabad 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.
hasCouncilAreaPart
Indicates that one council area includes another council area as a constituent part within its administrative or geographic boundaries.
-
D.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
E.
hasCouncilAreaStatusFrom
Indicates that an entity holds council area status starting from a specified point in time.
- 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_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 6:43 p.m.