Triple
T26352366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amersham station |
E662935
|
entity |
| Predicate | isOuterTerminusOf |
P107885
|
FINISHED |
| Object | Metropolitan line fast services |
—
|
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: Metropolitan line fast services | Statement: [Amersham station, isOuterTerminusOf, Metropolitan line fast services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOuterTerminusOf Context triple: [Amersham station, isOuterTerminusOf, Metropolitan line fast services]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
isMajorTerminalOf
Indicates that one entity serves as a primary or main terminal (such as a key endpoint or hub) for another entity within a system or network.
-
C.
hasTerminusRole
chosen
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
D.
hasOppositeTerminus
Indicates that one terminus (end point) of an entity is directly opposite or facing the terminus of another entity.
-
E.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fec2c3c8190b76c15fa8a97f0e6 |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:46 p.m.