Triple
T32630225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buntingford railway station |
E834183
|
entity |
| Predicate | servedModeOfTransport |
P86086
|
FINISHED |
| Object | rail |
—
|
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: rail | Statement: [Buntingford railway station, servedModeOfTransport, rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedModeOfTransport Context triple: [Buntingford railway station, servedModeOfTransport, rail]
-
A.
servedByTransportation
Indicates that a location or entity is provided access or connection by a particular mode or service of transportation.
-
B.
modeOfService
Indicates the manner, method, or channel through which a service is delivered or provided.
-
C.
usedTransportationMode
Indicates that an entity traveled or moved using a specified mode of transportation.
-
D.
transportationServedBy
Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
-
E.
transportModePresent
chosen
Indicates that a particular mode of transportation is involved or available in the described context or event.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 1, 2026, 1:07 a.m.