Triple
T37484777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transport in the East of England |
E931500
|
entity |
| Predicate | majorBusOperator |
P14541
|
FINISHED |
| Object | First Eastern Counties |
—
|
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: First Eastern Counties | Statement: [Transport in the East of England, majorBusOperator, First Eastern Counties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorBusOperator Context triple: [Transport in the East of England, majorBusOperator, First Eastern Counties]
-
A.
publicTransportOperatorFor
Indicates that one entity operates or manages public transportation services for another entity or area.
-
B.
hasBusOperator
chosen
Indicates that a bus service, route, or vehicle is operated or managed by a specific operator or company.
-
C.
hasBusServiceOperatorType
Indicates that a bus service is associated with a specific type or category of operator responsible for running it.
-
D.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
E.
transportOperator
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
- 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_69f76ec382248190b47844df596123c6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:17 p.m.