Triple
T138910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vernal Fall |
E2808
|
entity |
| Predicate | safetyRisk |
P1950
|
FINISHED |
| Object | slippery rocks |
—
|
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: slippery rocks | Statement: [Vernal Fall, safetyRisk, slippery rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRisk Context triple: [Vernal Fall, safetyRisk, slippery rocks]
-
A.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
B.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
C.
riskProfile
Indicates the level and characteristics of potential risk associated with an entity, action, or situation.
-
D.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
E.
securityFeature
Indicates that an entity provides, embodies, or is associated with a mechanism or property intended to enhance safety, protection, or defense against threats or vulnerabilities.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a800148190be119d1d075869b8 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.