Triple
T15928918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lore Lindu National Park |
E386272
|
entity |
| Predicate | bufferZoneUse |
P116763
|
FINISHED |
| Object | traditional agriculture |
—
|
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: traditional agriculture | Statement: [Lore Lindu National Park, bufferZoneUse, traditional agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bufferZoneUse Context triple: [Lore Lindu National Park, bufferZoneUse, traditional agriculture]
-
A.
bufferZone
Indicates the existence of an area or region that serves as a protective or separating space between two or more entities or activities.
-
B.
bufferZoneHectares
Indicates the size of the surrounding buffer zone measured in hectares.
-
C.
bufferZoneAreaSquareKilometres
Indicates the size of the surrounding buffer zone measured in square kilometres.
-
D.
bufferOwnershipModel
Indicates how responsibility for managing and releasing a data buffer is assigned between interacting components or systems.
-
E.
zonedUse
chosen
Indicates the designated or permitted type of land use assigned to a property or area under zoning regulations.
- 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_69d86da750008190987eb26be3f6c118 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e172b48b308190bc430b2308cbc75b |
completed | April 16, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69e142cf5c548190a931f7b58144cd31 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:52 a.m.