Triple
T36677613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London sewer system |
E905584
|
entity |
| Predicate | notablePumpingStation |
P10233
|
FINISHED |
| Object | Crossness Pumping Station |
E905585
|
NE 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: Crossness Pumping Station | Statement: [London sewer system, notablePumpingStation, Crossness Pumping Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePumpingStation Context triple: [London sewer system, notablePumpingStation, Crossness Pumping Station]
-
A.
hasPumpingStation
Indicates that one entity possesses, contains, or is served by a pumping station associated with it.
-
B.
oneOfLargestPowerStationsIn
Indicates that a power station is among the largest power stations located within a specified area or region.
-
C.
numberOfPumps
Indicates the quantity of pumps associated with or required by an entity or system.
-
D.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
-
E.
notablePlace
chosen
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- F. None of above.
Provenance (4 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a20dd836c8190b363a8ede247e929 |
completed | June 23, 2026, 5:59 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.