Triple
T10854355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tristania Falls |
E256231
|
entity |
| Predicate | isInProtectedAreaType |
P66888
|
FINISHED |
| Object | nationalPark |
—
|
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: nationalPark | Statement: [Tristania Falls, isInProtectedAreaType, nationalPark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInProtectedAreaType Context triple: [Tristania Falls, isInProtectedAreaType, nationalPark]
-
A.
isInProtectedArea
Indicates that an entity is located within a designated protected or conservation area.
-
B.
isProtectedAreaOf
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
-
C.
isInProtectedAreaVicinity
Indicates that an entity is located close to, but not necessarily within, a designated protected area.
-
D.
hasProtectedAreaCategory
chosen
Indicates that an area is assigned a specific protection or conservation category under a recognized protected area classification system.
-
E.
isProtectedAreaStatus
Indicates that an entity has a designated protection status, typically signifying legal or formal recognition as a protected 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_69d6aa83d1448190a66d93c32394d21f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751351a0c8190b38c14888c5e4275 |
completed | April 9, 2026, 7:11 a.m. |
| PD | Predicate disambiguation | batch_69d70d2b51448190bae748ed6c23edde |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:20 p.m.