Triple
T8708145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Risk |
E206702
|
entity |
| Predicate | hasDangerElement |
P63246
|
FINISHED |
| Object | risk to human testers |
—
|
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: risk to human testers | Statement: [Risk, hasDangerElement, risk to human testers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDangerElement Context triple: [Risk, hasDangerElement, risk to human testers]
-
A.
hasHazardLevel
Indicates that an entity is associated with a specified degree or category of risk or danger.
-
B.
hasObjectiveHazards
chosen
Indicates that an entity is associated with concrete, externally verifiable dangers or risks.
-
C.
hasNotableHazard
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
D.
hasNavigationHazard
Indicates that something presents or contains a condition, object, or feature that poses a risk or obstacle to safe navigation.
-
E.
hasSafetyCharacteristic
Indicates that an entity possesses a specific safety-related property, feature, or attribute.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58ffa6a481908866b6239d1d9b92 |
completed | March 31, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:35 p.m.