Triple
T15809232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 San Bruno pipeline explosion |
E383301
|
entity |
| Predicate | pipelineDesignation |
P81036
|
FINISHED |
| Object | Line 132 |
—
|
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: Line 132 | Statement: [2010 San Bruno pipeline explosion, pipelineDesignation, Line 132]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pipelineDesignation Context triple: [2010 San Bruno pipeline explosion, pipelineDesignation, Line 132]
-
A.
pipeline
Indicates a sequential process or workflow where the output of one stage is passed as input to the next to achieve a final result.
-
B.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
-
C.
pipeDiameter
Indicates that one entity specifies or measures the diameter of a pipe associated with another entity.
-
D.
plantDesignClass
Indicates a classification relationship where a plant is assigned to a particular design class or category based on its design characteristics.
-
E.
systemDesignation
chosen
Indicates that an entity has been assigned a specific formal label or identifier within a defined system or framework.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b529c6b481909664153ecc381f7c |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:48 a.m.