Triple
T27868110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mardale |
E704411
|
entity |
| Predicate | currentUnder |
P189335
|
FINISHED |
| Object | Haweswater Reservoir |
—
|
NE NERFINISHED |
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: Haweswater Reservoir | Statement: [Mardale, currentUnder, Haweswater Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUnder Context triple: [Mardale, currentUnder, Haweswater Reservoir]
-
A.
isCurrent
Indicates that something is presently valid, active, or up to date at the current point in time.
-
B.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
C.
currentRuler
Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
-
D.
currentOrdinary
Indicates that an entity currently holds or is in the state of an ordinary (non-special or non-exceptional) status or role.
-
E.
currentPosition
Indicates the present role, job, or status an entity currently holds within a given context.
- F. None of above. chosen
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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 27, 2026, 6:22 p.m.