Triple
T3793526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roc d’Azur |
E89712
|
entity |
| Predicate | safetyRequirements |
P20206
|
FINISHED |
| Object | helmet mandatory |
—
|
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: helmet mandatory | Statement: [Roc d’Azur, safetyRequirements, helmet mandatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyRequirements Context triple: [Roc d’Azur, safetyRequirements, helmet mandatory]
-
A.
safetyRequirement
chosen
Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
-
B.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
C.
safetyRelevant
Indicates that the associated entity, condition, or information has a direct impact on safety or is critical for preventing harm or accidents.
-
D.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
E.
safetyEquipment
Indicates that one entity serves as safety equipment used to protect another entity from harm or danger.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.