Triple
T27868092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale |
E704411
|
entity |
| Predicate | submergedFor |
P137846
|
FINISHED |
| Object | public water supply |
—
|
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: public water supply | Statement: [Mardale, submergedFor, public water supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: submergedFor Context triple: [Mardale, submergedFor, public water supply]
-
A.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
B.
submergedForPurpose
chosen
Indicates that one entity is intentionally placed or kept under a liquid or surface in order to achieve a specific purpose or outcome.
-
C.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
-
D.
formedBySubmerging
Indicates that something comes into existence or is created as a result of being placed or held beneath the surface of a liquid.
-
E.
submergedFeatures
Indicates that certain features or elements are located beneath the surface of a body of water or otherwise covered by liquid.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:22 p.m.