Triple
T28980736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wudongde Dam |
E734540
|
entity |
| Predicate | commissioningCompletionDate |
P56682
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Wudongde Dam, commissioningCompletionDate, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningCompletionDate Context triple: [Wudongde Dam, commissioningCompletionDate, 2021]
-
A.
commissioningEndDate
chosen
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
B.
commissioningEndYear
Indicates the calendar year in which the commissioning or initial operational phase of something is completed or ends.
-
C.
substantialCompletionDate
Indicates the date on which a project, work, or obligation is considered substantially complete, meaning the main required work has been finished to the point it can be used for its intended purpose.
-
D.
assemblyCompletionDate
Indicates the date on which the assembly process for an item or structure is finished.
-
E.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
- 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_69f05b0dd9b481908b7901e1c95ff6b2 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 9:11 a.m.