Triple
T30172011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinzua Bridge State Park |
E766944
|
entity |
| Predicate | mainStructureDamageEventDate |
P111853
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Kinzua Bridge State Park, mainStructureDamageEventDate, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStructureDamageEventDate Context triple: [Kinzua Bridge State Park, mainStructureDamageEventDate, 2003]
-
A.
firstBuildingDestructionDate
Indicates the date on which the first instance of a building’s destruction occurred in the given context or sequence of events.
-
B.
sufferedEventDate
chosen
Indicates the specific date on which an entity experienced or was affected by a particular event.
-
C.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
-
D.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
E.
mainStructurePartiallyDestroyedBy
Indicates that a primary structure has been damaged or destroyed to some extent as a result of the specified agent or event.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 7:24 p.m.