Triple
T25068813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapman's Peak |
E627852
|
entity |
| Predicate | hasRockfallProtection |
P69487
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Chapman's Peak, hasRockfallProtection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockfallProtection Context triple: [Chapman's Peak, hasRockfallProtection, yes]
-
A.
hasSlopeProtection
chosen
Indicates that a slope or embankment is equipped with protective measures or structures to prevent erosion, instability, or damage.
-
B.
hadMajorRockfall
Indicates that a significant rockfall event has occurred at or affected the subject entity.
-
C.
hasRockTalusAtBase
Indicates that a rock talus deposit is present at the base of something, typically accumulating at the bottom of a slope, cliff, or similar feature.
-
D.
hasProtectedAreaOnSlopes
Indicates that a designated protected area exists specifically on the slopes of a landform or terrain.
-
E.
hasClimbingHazard
Indicates that something presents a risk or danger specifically associated with climbing activities.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:10 a.m.