Triple
T19926441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lanín Volcano |
E478933
|
entity |
| Predicate | requiresClimbingPermit |
P19502
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lanín Volcano, requiresClimbingPermit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresClimbingPermit Context triple: [Lanín Volcano, requiresClimbingPermit, true]
-
A.
climbingPermitRequired
chosen
Indicates that performing a climbing activity at a given location or on a given route is contingent upon obtaining a formal permit or authorization.
-
B.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
C.
hasClimbingRestriction
Indicates that there is a rule, limitation, or prohibition affecting whether and how climbing is allowed on the associated object or location.
-
D.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
-
E.
hasClimbingTrail
Indicates that a location or area includes or provides access to a designated climbing trail.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659ca52c881908dc8053bf61be4c4 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.