Triple
T2486823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sariska Tiger Reserve |
E55945
|
entity |
| Predicate | bufferArea |
P4190
|
FINISHED |
| Object | approximately 368 square kilometres |
—
|
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: approximately 368 square kilometres | Statement: [Sariska Tiger Reserve, bufferArea, approximately 368 square kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bufferArea Context triple: [Sariska Tiger Reserve, bufferArea, approximately 368 square kilometres]
-
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.
areaBControl
Indicates that one entity has control or authority over a specific region or area labeled as B.
-
C.
areaAControl
Indicates that one entity exercises control or authority over a specified area or region.
-
D.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
E.
passesThroughArea
Indicates that an entity moves or extends through the spatial region defined by another entity or 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.