Triple
T15468650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidio Parkway |
E372096
|
entity |
| Predicate | replacedStructureWas |
P10258
|
FINISHED |
| Object | seismically deficient |
—
|
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: seismically deficient | Statement: [Presidio Parkway, replacedStructureWas, seismically deficient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedStructureWas Context triple: [Presidio Parkway, replacedStructureWas, seismically deficient]
-
A.
replacedStructure
chosen
Indicates that one structure has been substituted for, or taken the place of, another structure.
-
B.
replacedStructureType
Indicates that one structure type has been substituted or superseded by another structure type.
-
C.
replacedStructureDamagedBy
Indicates that a structure which has been replaced is (or was) damaged by a specified agent, event, or condition.
-
D.
replacedStructureOpened
Indicates that a previously existing structure has been removed or superseded and the new replacement structure has been opened or put into service.
-
E.
replacedStructureDemolished
Indicates that a structure which has been replaced by another has subsequently been demolished.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f69a31c81909a749247b6615d91 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.