Triple
T7913322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pooley Bridge |
E183752
|
entity |
| Predicate | bridgeDestructionYear |
P59878
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Pooley Bridge, bridgeDestructionYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeDestructionYear Context triple: [Pooley Bridge, bridgeDestructionYear, 2015]
-
A.
destroyedCityYear
Indicates that a specific city was destroyed in a particular year.
-
B.
originalBridgeDestroyed
chosen
Indicates that the initially existing bridge in a given context has been destroyed.
-
C.
demolitionYearApprox
Indicates that an entity was demolished in or around a particular year, where the year is an approximate rather than an exact value.
-
D.
demolishedAfter
Indicates that one entity was demolished at a point in time later than the demolition of another entity.
-
E.
demolishedAfterEvent
Indicates that one entity (typically a structure) was demolished after the occurrence of a specified 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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a748f4c8190bcd868de2fcf0b3a |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:04 p.m.