Triple
T10160244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elan Valley |
E233869
|
entity |
| Predicate | laterDamCompletionDate |
P92346
|
FINISHED |
| Object | 1952 |
—
|
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: 1952 | Statement: [Elan Valley, laterDamCompletionDate, 1952]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDamCompletionDate Context triple: [Elan Valley, laterDamCompletionDate, 1952]
-
A.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
B.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
-
C.
assemblyCompletionDate
Indicates the date on which the assembly process for an item or structure is finished.
-
D.
archCompletionDate
Indicates the date on which an architectural element, project, or structure was completed.
-
E.
dateFinalized
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5831e481909b48fdfa8f1c670b |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8f869c8190a82ad040993e0244 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:09 p.m.