Triple
T5241791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tadoba Andhari Tiger Reserve |
E118358
|
entity |
| Predicate | hasBufferZone |
P4190
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tadoba Andhari Tiger Reserve, hasBufferZone, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBufferZone Context triple: [Tadoba Andhari Tiger Reserve, hasBufferZone, yes]
-
A.
bufferZone
chosen
Indicates the existence of an area or region that serves as a protective or separating space between two or more entities or activities.
-
B.
hasFreeZone
Indicates that an entity includes or is associated with a designated free zone area where special rules, privileges, or exemptions apply.
-
C.
hasZone
Indicates that one entity possesses, contains, or is associated with a specific zone or designated area.
-
D.
bufferZoneHectares
Indicates the size of the surrounding buffer zone measured in hectares.
-
E.
hasUNESCOWorldHeritageBufferZone
Indicates that an entity has an officially designated buffer zone associated with a UNESCO World Heritage site, typically providing additional protection around the core heritage area.
- 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_69bd4467db0881909b3b0982df32cc8f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4c6fa8819099442b1b110e51fb |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.