Triple
T37937904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesotho Highlands Water Project |
E946397
|
entity |
| Predicate | secondaryDam |
P200894
|
FINISHED |
| Object | Mohale Dam |
—
|
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: Mohale Dam | Statement: [Lesotho Highlands Water Project, secondaryDam, Mohale Dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryDam Context triple: [Lesotho Highlands Water Project, secondaryDam, Mohale Dam]
-
A.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryIssue
Indicates that one issue is related to another as a subordinate, less primary, or follow-up concern in the overall context.
-
D.
secondaryFire
Indicates the use or activation of an alternate or secondary mode of firing in a weapon or tool, distinct from its primary fire action.
-
E.
secondaryGround
Indicates a secondary or auxiliary grounding connection or reference point associated with the primary ground.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
| PDg | Predicate description generation | batch_69ffb6976f84819098a9b14946591baa |
completed | May 9, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:20 p.m.