Triple
T31843918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holt |
E812881
|
entity |
| Predicate | hasHistoricBridgeOver |
P127343
|
FINISHED |
| Object | River Dee |
—
|
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: River Dee | Statement: [Holt, hasHistoricBridgeOver, River Dee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBridgeOver Context triple: [Holt, hasHistoricBridgeOver, River Dee]
-
A.
isHistoricBridgeOf
chosen
Indicates that a bridge has historical significance and serves or served as a notable crossing associated with a particular place or route.
-
B.
isOldestSurvivingBridgeAcross
Indicates that a bridge is the most ancient still-existing bridge that spans a specified waterway, road, or gap.
-
C.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
D.
openedHistoricBridgeTo
Indicates that an entity initiated public access or use of a bridge recognized as historic.
-
E.
hasDrawbridge
Indicates that one entity possesses or is equipped with a drawbridge as part of its structure or features.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 30, 2026, 11:50 p.m.