Triple
T24219780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HBY |
E601414
|
entity |
| Predicate | networkOfStationIdentified |
P111734
|
FINISHED |
| Object | London Underground |
—
|
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 Underground | Statement: [HBY, networkOfStationIdentified, London Underground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: networkOfStationIdentified Context triple: [HBY, networkOfStationIdentified, London Underground]
-
A.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
-
B.
networkAffiliationOfStation
Indicates that a particular broadcast station is affiliated with, or part of, a specific television or radio network.
-
C.
associatedStation
Indicates a relationship where one entity is linked or connected to a particular station as its relevant or related station.
-
D.
isRailwayStationInNetwork
chosen
Indicates that a railway station belongs to, and is served as part of, a particular railway network.
-
E.
networkBrandingOfStationServed
Indicates the branding or network identity under which a station operates or is presented when it is served.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.