Triple
T8749343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tunnel No. 1 |
E207915
|
entity |
| Predicate | hazardIfFailed |
P16293
|
FINISHED |
| Object | disruption of New York City water supply |
—
|
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: disruption of New York City water supply | Statement: [Tunnel No. 1, hazardIfFailed, disruption of New York City water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hazardIfFailed Context triple: [Tunnel No. 1, hazardIfFailed, disruption of New York City water supply]
-
A.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
hasFailureProbability
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
D.
hasNotableHazard
chosen
Indicates that an entity is associated with a significant risk, danger, or harmful condition that is noteworthy or exceptional.
-
E.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da4214881908b6917f847c43cb5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.