Triple
T11131414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manette Bridge |
E263290
|
entity |
| Predicate | oldStructureDemolished |
P51835
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Manette Bridge, oldStructureDemolished, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oldStructureDemolished Context triple: [Manette Bridge, oldStructureDemolished, 2011]
-
A.
demolishedOriginalStructures
Indicates that one entity has completely destroyed or removed the original structures associated with another entity.
-
B.
previousBuildingDemolished
chosen
Indicates that a building which previously occupied the same site or fulfilled the same role has been demolished.
-
C.
mostStructuresDemolished
Indicates that the subject is the entity responsible for demolishing the greatest number of structures within a given context or set.
-
D.
demolishedWith
Indicates that one entity was destroyed or torn down using another specified tool, method, or agent.
-
E.
demolishedOrDestroyed
Indicates that one entity has caused another entity to be torn down, ruined, or rendered unusable, typically through deliberate demolition or destructive force.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e831f4808190afabdaa0e97bbe32 |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.