Triple
T32334995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sudbrook |
E826146
|
entity |
| Predicate | pumpingStationPowerSource |
P8164
|
FINISHED |
| Object | steam engines (historically) |
—
|
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: steam engines (historically) | Statement: [Sudbrook, pumpingStationPowerSource, steam engines (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pumpingStationPowerSource Context triple: [Sudbrook, pumpingStationPowerSource, steam engines (historically)]
-
A.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
B.
isMajorSourceOfElectricityFor
Indicates that one entity provides the primary or dominant share of electrical power used by another entity.
-
C.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
D.
hasPowerSource
chosen
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
E.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
- 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_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:48 a.m.