Triple
T29890205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertford North |
E759129
|
entity |
| Predicate | servedByPeakHourServicesTo |
P103734
|
FINISHED |
| Object | London King’s Cross |
—
|
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: London King’s Cross | Statement: [Hertford North, servedByPeakHourServicesTo, London King’s Cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedByPeakHourServicesTo Context triple: [Hertford North, servedByPeakHourServicesTo, London King’s Cross]
-
A.
servedByRushHourService
chosen
Indicates that the entity is provided or operated by a rush hour (peak-time) transit service.
-
B.
servedByLateEveningServicesTo
Indicates that the subject location is provided with transportation or service connections to the object location specifically during late evening hours.
-
C.
typicalOffPeakServiceTo
Indicates the usual or standard off-peak (non-peak time) service pattern that operates to a given destination.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
trafficServed
Indicates that a system, component, or entity handles, processes, or carries a specified amount or type of traffic (e.g., network, data, or user requests).
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 29, 2026, 6:02 p.m.