Triple
T30000798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Koka |
E762160
|
entity |
| Predicate | completionOfAssociatedDam |
P173271
|
FINISHED |
| Object | 1960 |
—
|
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: 1960 | Statement: [Lake Koka, completionOfAssociatedDam, 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completionOfAssociatedDam Context triple: [Lake Koka, completionOfAssociatedDam, 1960]
-
A.
completedWithDam
Indicates that an action, project, or process was completed through the use or involvement of a dam.
-
B.
associatedDam
Indicates a relationship where one entity is linked or connected to a specific dam, typically as its related or corresponding dam structure.
-
C.
laterDamCompletionDate
Indicates that one dam’s completion date occurs chronologically after another dam’s completion date.
-
D.
associatedDamType
Indicates that there is a specific type or classification of dam linked or related to the referenced entity.
-
E.
firstDamsCompleted
Indicates that the referenced dams are the earliest ones to have been completed within a given context, such as a region, project, or time period.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 29, 2026, 6:41 p.m.