Triple
T33593537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Central |
E860495
|
entity |
| Predicate | operatesBusServicesAsPartOf |
P14541
|
FINISHED |
| Object | London Buses network |
—
|
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 Buses network | Statement: [London Central, operatesBusServicesAsPartOf, London Buses network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesBusServicesAsPartOf Context triple: [London Central, operatesBusServicesAsPartOf, London Buses network]
-
A.
operatesInterurbanBusServices
Indicates that an entity runs or manages bus transportation services operating between different towns or cities within a region.
-
B.
hasBusServices
Indicates that one location or entity is served by bus routes or bus transportation provided by another.
-
C.
hasBusServiceOperatorType
Indicates that a bus service is associated with a specific type or category of operator responsible for running it.
-
D.
operatedPassengerServices
Indicates that an entity provided and managed transportation services specifically for carrying passengers.
-
E.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
- 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_69f3497e70e48190951c94d072879bec |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0079e152648190a9da2add94fc1831 |
completed | May 10, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a0078f77f9c8190af357a6016a2bd53 |
completed | May 10, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:41 a.m.