Triple
T27799699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhati |
E702205
|
entity |
| Predicate | associatedWithDesertRegion |
P37774
|
FINISHED |
| Object | Thar Desert |
—
|
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: Thar Desert | Statement: [Bhati, associatedWithDesertRegion, Thar Desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDesertRegion Context triple: [Bhati, associatedWithDesertRegion, Thar Desert]
-
A.
hasNearbyDesert
chosen
Indicates that one entity is located close to or in the vicinity of a desert region associated with another entity.
-
B.
desertsFrom
Indicates that an entity abandons or leaves allegiance to another entity, typically in a disloyal or unauthorized manner.
-
C.
isLocatedInDesert
Indicates that something exists or is situated within a desert region or environment.
-
D.
locatedInDesertTransitionZone
Indicates that something is situated in a geographical area where desert conditions gradually transition into a different type of ecosystem.
-
E.
associatedDesertRoute
Indicates a relationship where an entity is linked to, or connected with, a specific desert route, such as a path, trail, or corridor through a desert 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: April 27, 2026, 5:33 p.m.