Triple
T5997206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caterham railway station |
E133499
|
entity |
| Predicate | isSuburbanTerminus |
P49504
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Caterham railway station, isSuburbanTerminus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuburbanTerminus Context triple: [Caterham railway station, isSuburbanTerminus, yes]
-
A.
isSuburbanStationOf
Indicates that a station is located in a suburban area and functionally serves as a subsidiary or outlying station of a main or central station.
-
B.
hasSuburbanPlatforms
Indicates that an entity (typically a railway station or transit hub) includes platforms specifically designated for suburban or commuter train services.
-
C.
isInSuburbanArea
chosen
Indicates that something is located within a suburban area, typically between urban and rural regions.
-
D.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
E.
isSuburbanCityOf
Indicates that one city is a suburban municipality that is part of, or closely associated with, a larger primary city or metropolitan area.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04ee274e08190b6478c7ae318ae48 |
completed | March 22, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.