Triple
T37890170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Granville Bridge |
E945109
|
entity |
| Predicate | hasSeismicUpgrades |
P13028
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Granville Bridge, hasSeismicUpgrades, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeismicUpgrades Context triple: [Granville Bridge, hasSeismicUpgrades, yes]
-
A.
hasSeismicBehavior
Indicates that an entity exhibits or is characterized by a particular type or pattern of seismic activity or response.
-
B.
seismicRetrofit
chosen
Indicates that an existing structure has been modified or strengthened to improve its performance and safety during seismic events such as earthquakes.
-
C.
earthquakeResistance
Indicates how well an entity can withstand or remain functional during an earthquake without significant damage.
-
D.
seismicSafetyConcernsIdentified
Indicates that potential risks or issues related to seismic safety have been detected or recognized.
-
E.
seismicDesignCategory
Indicates the classification of a structure’s required level of seismic resistance based on its expected exposure to earthquake forces.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00ada2903481908b28ce55ef97a6c2 |
completed | May 10, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_6a00ad5d23788190b3f9e2de761d39bb |
completed | May 10, 2026, 4:07 p.m. |
Created at: May 3, 2026, 4:19 p.m.