Triple
T36810250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protesters Falls |
E909567
|
entity |
| Predicate | hasSafetyNotice |
P97409
|
FINISHED |
| Object | slippery rocks hazard |
—
|
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 hazard | Statement: [Protesters Falls, hasSafetyNotice, slippery rocks hazard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSafetyNotice Context triple: [Protesters Falls, hasSafetyNotice, slippery rocks hazard]
-
A.
hasSafetyInformation
chosen
Indicates that one entity provides or is associated with safety-related details, warnings, or guidelines about another entity.
-
B.
notableSafety
Indicates that an entity is recognized for having significant safety characteristics, performance, or impact relative to others.
-
C.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
-
D.
hasSafetyDesignation
Indicates that an entity has been assigned a specific safety-related classification or status.
-
E.
hasSafetyCertificate
Indicates that an entity possesses or has been granted a valid safety certificate.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:13 p.m.