Triple
T37937901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesotho Highlands Water Project |
E946397
|
entity |
| Predicate | phaseICompletion |
P29875
|
FINISHED |
| Object | early 2000s |
—
|
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: early 2000s | Statement: [Lesotho Highlands Water Project, phaseICompletion, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseICompletion Context triple: [Lesotho Highlands Water Project, phaseICompletion, early 2000s]
-
A.
majorPhaseCompletion
chosen
Indicates that a significant or primary phase of a larger process, project, or lifecycle has been fully completed.
-
B.
secondPhaseCompletion
Indicates that a process, project, or operation has finished its second phase or stage.
-
C.
phase2Terminus
Indicates that an entity serves as the endpoint or final state of a second phase in a multi-phase process or sequence.
-
D.
phase1Purpose
Indicates that one entity serves as the specific purpose, goal, or intended outcome of the first phase of another entity, process, or project.
-
E.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.