Triple
T35104482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow–Helensburgh route |
E1013110
|
entity |
| Predicate | servesBankOfRiver |
P201394
|
FINISHED |
| Object | north bank of the River Clyde |
—
|
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: north bank of the River Clyde | Statement: [Glasgow–Helensburgh route, servesBankOfRiver, north bank of the River Clyde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBankOfRiver Context triple: [Glasgow–Helensburgh route, servesBankOfRiver, north bank of the River Clyde]
-
A.
servesBank
Indicates that one entity provides banking or financial services to another entity.
-
B.
riverBankOne
Indicates that the referenced entity is one specific side or bank of a river, typically the first or primary one in a pairwise relation.
-
C.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
D.
riverBankTerminus
Indicates the location where a river meets or ends at a bank or shoreline boundary.
-
E.
riverBankOnSouthSide
Indicates that a river bank is located on the southern side of a specified river or watercourse.
- F. None of above. chosen
Provenance (4 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fff09dae088190bd8460060d778feb |
completed | May 10, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69fff0027c5c8190baa5c7a15852cbe0 |
completed | May 10, 2026, 2:40 a.m. |
| PDg | Predicate description generation | batch_69fff09ce63881908e7f91a3d35d969f |
completed | May 10, 2026, 2:42 a.m. |
Created at: May 3, 2026, 4:01 p.m.