Triple
T27180420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Periyar Tiger Reserve |
E683174
|
entity |
| Predicate | coreAreaSize |
P59696
|
FINISHED |
| Object | approximately 350 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 350 square kilometres | Statement: [Periyar Tiger Reserve, coreAreaSize, approximately 350 square kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreAreaSize Context triple: [Periyar Tiger Reserve, coreAreaSize, approximately 350 square kilometres]
-
A.
coreAreaOf
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
B.
coveredArea
Indicates that one entity occupies or extends over a specific spatial region or surface area associated with another entity.
-
C.
coreZoneArea
chosen
Indicates the area or spatial extent of a designated core zone within a larger region or system.
-
D.
areaCControl
Indicates that an entity exercises control or authority over a specific geographic area or region.
-
E.
effectiveArea
Indicates the portion of a surface or region that actually contributes to a specified effect, such as performance, interaction, or impact, within a given context.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6257cec68819089da3874cf1ac740 |
completed | May 2, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:28 a.m.