Triple
T27868124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale |
E704411
|
entity |
| Predicate | reservoirCompleted |
P39983
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Mardale, reservoirCompleted, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservoirCompleted Context triple: [Mardale, reservoirCompleted, 1935]
-
A.
reservoirCreated
chosen
Indicates that a reservoir has been brought into existence, typically through construction or formation by some agent or process.
-
B.
reservoir
Indicates that one entity serves as a storage or containment source (often for a resource) that can supply or affect another entity.
-
C.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
-
D.
usesReservoir
Indicates that one entity draws upon, depends on, or operates using a particular reservoir as a resource or source.
-
E.
inReservoirSystem
Indicates that one entity is part of, contained within, or managed by a particular reservoir system.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:22 p.m.