Triple
T16323433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O'Neill Tunnel |
E396353
|
entity |
| Predicate | hasFireSuppression |
P18626
|
FINISHED |
| Object | fire protection systems |
—
|
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: fire protection systems | Statement: [O'Neill Tunnel, hasFireSuppression, fire protection systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFireSuppression Context triple: [O'Neill Tunnel, hasFireSuppression, fire protection systems]
-
A.
hasFireControlSystem
chosen
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
-
B.
isLessFlammableThan
Indicates that one entity has a lower tendency to catch fire or burn than another entity.
-
C.
canControlFlames
Indicates the ability of one entity to generate, manipulate, or otherwise exert control over fire or flames.
-
D.
isNonCombustible
Indicates that the subject does not burn or support combustion under normal conditions.
-
E.
fireCoverage
Indicates the extent to which an area or object is protected or served by fire prevention, detection, or suppression resources.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b82fe88190a448597b7827f859 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.