Triple
T37405071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Buses route 35 |
E929103
|
entity |
| Predicate | hasServiceProviderContract |
P27052
|
FINISHED |
| Object | TfL bus tendering system |
—
|
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: TfL bus tendering system | Statement: [London Buses route 35, hasServiceProviderContract, TfL bus tendering system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceProviderContract Context triple: [London Buses route 35, hasServiceProviderContract, TfL bus tendering system]
-
A.
hasServiceProvider
Indicates that an entity is associated with or supported by a specific service provider.
-
B.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
C.
hasContractWith
chosen
Indicates that one entity is bound by a formal contract or agreement with another entity.
-
D.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
E.
isContractedBy
Indicates that an entity (such as a service, work, or obligation) is formally engaged or commissioned through a contract by another entity.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:16 p.m.