Triple
T31211701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rufford Branch |
E795760
|
entity |
| Predicate | connectsTowards |
P159755
|
FINISHED |
| Object | Ribble estuary |
—
|
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: Ribble estuary | Statement: [Rufford Branch, connectsTowards, Ribble estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTowards Context triple: [Rufford Branch, connectsTowards, Ribble estuary]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
C.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
D.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
-
E.
terminusTowards
chosen
Indicates that one entity serves as the endpoint or directional terminus oriented toward another 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 29, 2026, 9:09 p.m.