Triple
T7085364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Tiger reserve |
E165060
|
entity |
| Predicate | hasBufferArea |
P4190
|
FINISHED |
| Object | buffer zone |
—
|
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: buffer zone | Statement: [Project Tiger reserve, hasBufferArea, buffer zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBufferArea Context triple: [Project Tiger reserve, hasBufferArea, buffer zone]
-
A.
hasWaitingArea
Indicates that an entity provides or includes a designated space where people can wait before receiving a service or proceeding to another area.
-
B.
hasPortArea
Indicates that an entity possesses or is associated with a specific port area, typically representing the spatial extent or boundary of its port facilities.
-
C.
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.
-
D.
hasWorkArea
Indicates that one entity possesses, is assigned, or is associated with a specific physical or conceptual work area.
-
E.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
- 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_69c6887d98408190912b9580666b0c1d |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e511535c819098f60de54930380f |
completed | March 27, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c172148190bf290c07bf579d1f |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:41 p.m.