Triple
T30490288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twyford railway station |
E775838
|
entity |
| Predicate | servesBranchTerminus |
P43881
|
FINISHED |
| Object | Henley-on-Thames |
—
|
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: Henley-on-Thames | Statement: [Twyford railway station, servesBranchTerminus, Henley-on-Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBranchTerminus Context triple: [Twyford railway station, servesBranchTerminus, Henley-on-Thames]
-
A.
servesBranch
Indicates that one entity provides services or support to a particular branch or subdivision of an organization.
-
B.
servedByRailBranch
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
-
C.
servesJunction
Indicates that one element functions as a connecting or branching point where multiple other elements meet or intersect.
-
D.
locatedAtTerminusOf
chosen
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
E.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 29, 2026, 8:13 p.m.