Triple
T11234759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta Low Dam III |
E265913
|
entity |
| Predicate | projectStage |
P44772
|
FINISHED |
| Object | Stage III of Teesta Low Dam projects |
—
|
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: Stage III of Teesta Low Dam projects | Statement: [Teesta Low Dam III, projectStage, Stage III of Teesta Low Dam projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectStage Context triple: [Teesta Low Dam III, projectStage, Stage III of Teesta Low Dam projects]
-
A.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
C.
investmentStage
Indicates the phase or maturity level a company or project is in with respect to receiving investment or funding.
-
D.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
E.
constructionPhase
chosen
Indicates the specific stage or period an entity is in within an overall construction or building process.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.