Triple
T26149333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Buses route 42 |
E659770
|
entity |
| Predicate | operatedUnderContractBy |
P62102
|
FINISHED |
| Object | London Central |
—
|
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 Central | Statement: [London Buses route 42, operatedUnderContractBy, London Central]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderContractBy Context triple: [London Buses route 42, operatedUnderContractBy, London Central]
-
A.
oftenOperatedBy
Indicates that an entity is frequently or typically operated, controlled, or run by another entity.
-
B.
alsoOperatedBy
Indicates that an entity is additionally operated or managed by another operator, alongside any primary or other operators.
-
C.
operatedUnderUmbrellaOf
Indicates that one entity functions, acts, or is managed within the organizational, legal, or brand framework and authority of another overarching entity.
-
D.
operatedByCompany
chosen
Indicates that an entity is run, managed, or controlled by a specific company.
-
E.
operatedAs
Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: April 26, 2026, 8:24 p.m.