Triple
T38171759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldgate Pump |
E1000092
|
entity |
| Predicate | waterSupplyCeased |
P26834
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Aldgate Pump, waterSupplyCeased, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSupplyCeased Context triple: [Aldgate Pump, waterSupplyCeased, 19th century]
-
A.
causedWaterSupplyDisruption
Indicates that one entity was responsible for interrupting or impairing another entity’s water supply.
-
B.
waterFunction
Indicates that one entity serves a particular role, purpose, or function in relation to water (e.g., how it uses, manages, affects, or interacts with water).
-
C.
waterSupplyProjectFor
Indicates that a water supply project is undertaken for the benefit or service of a particular entity.
-
D.
waterLossCause
Indicates that one entity is the cause or source of another entity’s loss of water.
-
E.
hasWaterManagementIssue
chosen
Indicates that an entity experiences problems or challenges related to the control, distribution, quality, or availability of water.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:29 p.m.