Triple
T36212128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teesta Stage III Hydroelectric Project |
E1047579
|
entity |
| Predicate | projectStageNumber |
P114525
|
FINISHED |
| Object | Stage III |
—
|
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 | Statement: [Teesta Stage III Hydroelectric Project, projectStageNumber, Stage III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectStageNumber Context triple: [Teesta Stage III Hydroelectric Project, projectStageNumber, Stage III]
-
A.
projectNumber
Indicates a relationship where a specific identifying number is assigned to or associated with a particular project.
-
B.
numberOfStages
Indicates the total count of distinct stages or phases associated with a given process, event, or entity.
-
C.
developmentPhaseName
chosen
Indicates the specific stage or phase name within a broader development process or lifecycle.
-
D.
numberPerStage
Indicates the quantity or count associated with each distinct stage in a multi-stage process or sequence.
-
E.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.