Triple
T522226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ribble |
E10841
|
entity |
| Predicate | notableBridge |
P386
|
FINISHED |
| Object | Ribblehead Viaduct vicinity |
—
|
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: Ribblehead Viaduct vicinity | Statement: [River Ribble, notableBridge, Ribblehead Viaduct vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBridge Context triple: [River Ribble, notableBridge, Ribblehead Viaduct vicinity]
-
A.
bridges
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
-
B.
hasMajorBridge
chosen
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
hasNotableBridgeType
Indicates that an entity is associated with a specific, noteworthy type or design category of bridge.
-
E.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1b372408190b3918fec45444674 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f018129c81909494450fcba71b59 |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.