Triple
T27903589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telangana–Maharashtra border |
E705705
|
entity |
| Predicate | hasNearbyTribalRegion |
P86469
|
FINISHED |
| Object | Adilabad tribal areas |
—
|
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: Adilabad tribal areas | Statement: [Telangana–Maharashtra border, hasNearbyTribalRegion, Adilabad tribal areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyTribalRegion Context triple: [Telangana–Maharashtra border, hasNearbyTribalRegion, Adilabad tribal areas]
-
A.
hasNearbyTribalLand
Indicates that an entity is located close to or adjacent to land officially recognized as belonging to a tribal nation or indigenous community.
-
B.
hasTribalHeadquartersNearby
Indicates that the subject entity is located close to the tribal headquarters of a Native nation or tribe.
-
C.
associatedTribeLocation
Indicates a relationship where a tribe is linked or connected to a specific geographic location.
-
D.
hasNearbyTown
Indicates that one location has a town situated close to it in geographic proximity.
-
E.
nearTribalGroup
chosen
Indicates that one entity is located geographically close to a tribal group.
- 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_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 27, 2026, 6:43 p.m.