Triple
T38180183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bartonsville, Vermont |
E1005134
|
entity |
| Predicate | coveredBridgeName |
P26021
|
FINISHED |
| Object | Bartonsville Covered Bridge |
—
|
NE NERFINISHED |
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: Bartonsville Covered Bridge | Statement: [Bartonsville, Vermont, coveredBridgeName, Bartonsville Covered Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredBridgeName Context triple: [Bartonsville, Vermont, coveredBridgeName, Bartonsville Covered Bridge]
-
A.
coveredBridgeBuilt
Indicates that a covered bridge was constructed or brought into existence.
-
B.
originalBridgeNickname
Indicates that an entity is the original or primary source of a particular bridge nickname assigned to another entity.
-
C.
bridgeNickname
Indicates that one entity is an alternative or informal nickname used to refer to another entity, serving as a bridge between different name forms.
-
D.
bridgeName
chosen
Indicates the designated name assigned to a specific bridge.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:29 p.m.