Triple
T6423464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport Pagnell |
E127999
|
entity |
| Predicate | Tickford BridgeInstanceOf |
P1787
|
FINISHED |
| Object | iron bridge |
—
|
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: iron bridge | Statement: [Newport Pagnell, Tickford BridgeInstanceOf, iron bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tickford BridgeInstanceOf Context triple: [Newport Pagnell, Tickford BridgeInstanceOf, iron bridge]
-
A.
hasFootbridge
Indicates that there exists a footbridge providing a pedestrian connection between the related entities.
-
B.
bridgeType
chosen
Indicates the specific kind or classification of a bridge associated with an entity.
-
C.
tollBridge
Indicates that passage across a bridge requires payment of a toll or fee.
-
D.
hasSubmersibleBridge
Indicates that one entity possesses or includes a bridge structure designed to be lowered or submerged, typically to allow passage over or through water.
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_69c00838de888190af2eec0b80495efa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c06906eea88190a445c1ff1169c2b1 |
completed | March 22, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69c060f780b08190aa650b4d1fc51f21 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:43 p.m.