Triple
T35638845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Buses route 367 |
E1029798
|
entity |
| Predicate | operatorContractedBy |
P143046
|
FINISHED |
| Object | Transport for London |
—
|
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: Transport for London | Statement: [London Buses route 367, operatorContractedBy, Transport for London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorContractedBy Context triple: [London Buses route 367, operatorContractedBy, Transport for London]
-
A.
isContractedBy
chosen
Indicates that an entity (such as a service, work, or obligation) is formally engaged or commissioned through a contract by another entity.
-
B.
managedUnderContractWith
Indicates that one entity is responsible for managing another entity or service based on the terms of a formal contract with a specified party.
-
C.
mayContractWith
Indicates that one entity is permitted or authorized to enter into a contractual agreement with another entity.
-
D.
hasOperatorContractAuthority
Indicates that an entity has the legal or formal authority to enter into and manage operator contracts on behalf of another party or organization.
-
E.
hasOperatorContractStart
Indicates the date on which an operator’s contractual agreement with another entity begins.
- 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_69f76e087bdc8190a4794bf9c0bd7634 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.