Triple
T38160951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco Docklands |
E953016
|
entity |
| Predicate | operatedRailwaySystem |
P176692
|
FINISHED |
| Object | automated light metro |
—
|
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: automated light metro | Statement: [Serco Docklands, operatedRailwaySystem, automated light metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedRailwaySystem Context triple: [Serco Docklands, operatedRailwaySystem, automated light metro]
-
A.
transitSystemTypeOperated
chosen
Indicates the type of transit system that an operator runs or manages.
-
B.
operatesRailNetworkOf
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
C.
operatedOnRailroad
Indicates that an entity conducted operations or provided services on a railroad system.
-
D.
railwaySystemServed
Indicates that a railway system provides service to, or operates within, a specified location or area.
-
E.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
- 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_69f76f0b93c48190a117319ab3a9f282 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a035052a47081908e9e56e21c543d46 |
completed | May 12, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a034d306e588190a2dce906fd46eb54 |
completed | May 12, 2026, 3:54 p.m. |
Created at: May 3, 2026, 4:21 p.m.