Triple
T38160965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serco Docklands |
E953016
|
entity |
| Predicate | servedStationArea |
P100437
|
FINISHED |
| Object | Canary Wharf |
—
|
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: Canary Wharf | Statement: [Serco Docklands, servedStationArea, Canary Wharf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedStationArea Context triple: [Serco Docklands, servedStationArea, Canary Wharf]
-
A.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
B.
regionServedByStation
chosen
Indicates that a particular geographic region is within the service coverage area of a given station.
-
C.
nearbyAreaServed
Indicates that a location or entity provides services or coverage to an adjacent or nearby area.
-
D.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
E.
regionServedFromHub
Indicates that a particular region receives its services, operations, or logistical support from a specified hub location.
- 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_6a009273634c8190b5b9c87053b56760 |
completed | May 10, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_6a0092171230819096e4274dd97e0410 |
completed | May 10, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4:21 p.m.