Triple
T38180185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartonsville, Vermont |
E1005134
|
entity |
| Predicate | coveredBridgeRebuiltAfter |
P157588
|
FINISHED |
| Object | 2011 Vermont floods |
—
|
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 Vermont floods | Statement: [Bartonsville, Vermont, coveredBridgeRebuiltAfter, 2011 Vermont floods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredBridgeRebuiltAfter Context triple: [Bartonsville, Vermont, coveredBridgeRebuiltAfter, 2011 Vermont floods]
-
A.
coveredBridgeBuilt
Indicates that a covered bridge was constructed or brought into existence.
-
B.
bridgeRebuilt
chosen
Indicates that a previously existing bridge has been reconstructed or restored after damage, destruction, or disuse.
-
C.
rebuiltAsLiftBridge
Indicates that an existing structure was reconstructed or converted into a lift bridge.
-
D.
originalBridgeDestroyed
Indicates that the initially existing bridge in a given context has been destroyed.
-
E.
oldBridgeClosed
Indicates that an old bridge is no longer open or available for use, typically due to safety, maintenance, or regulatory reasons.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: May 3, 2026, 4:29 p.m.