Triple
T32334994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudbrook |
E826146
|
entity |
| Predicate | pumpingStationLocation |
P82120
|
FINISHED |
| Object | Severn Tunnel Sudbrook pumping station |
—
|
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: Severn Tunnel Sudbrook pumping station | Statement: [Sudbrook, pumpingStationLocation, Severn Tunnel Sudbrook pumping station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpingStationLocation Context triple: [Sudbrook, pumpingStationLocation, Severn Tunnel Sudbrook pumping station]
-
A.
hasPumpingStation
chosen
Indicates that one entity possesses, contains, or is served by a pumping station associated with it.
-
B.
gasSystemLocation
Indicates the physical place or area where a gas system is installed, situated, or operates.
-
C.
meterLocation
Indicates the physical placement or position of a meter relative to the object or environment it is associated with.
-
D.
fuelTransferLocation
Indicates the place or facility where fuel is transferred from one container, vehicle, or system to another.
-
E.
originalStationLocation
Indicates the location where a station was initially established or first situated.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1779cc8190abe386c03d31d385 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.