Triple
T19976014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashopton |
E493691
|
entity |
| Predicate | evacuatedFor |
P87484
|
FINISHED |
| Object | construction of Ladybower Reservoir |
—
|
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: construction of Ladybower Reservoir | Statement: [Ashopton, evacuatedFor, construction of Ladybower Reservoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evacuatedFor Context triple: [Ashopton, evacuatedFor, construction of Ladybower Reservoir]
-
A.
evacuatedDuring
Indicates that one entity was removed or relocated from a place or situation during the time period or event represented by the other entity.
-
B.
evacuatedBy
Indicates that an entity is removed or cleared from a place or situation through the action or assistance of another agent or process.
-
C.
evacuationReason
chosen
Indicates the cause or justification for why an evacuation took place or was required.
-
D.
evacuationOrderedIn
Indicates that an official evacuation has been ordered to occur within a specified location or area.
-
E.
numberOfEvacuated
Indicates the total count of individuals who have been evacuated from a location or situation.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d0f4fb48190ad63afeff3513523 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:26 p.m.