Triple
T33372929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arun III Hydroelectric Project |
E854546
|
entity |
| Predicate | projectCapacity |
P113716
|
FINISHED |
| Object | 900 MW |
—
|
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: 900 MW | Statement: [Arun III Hydroelectric Project, projectCapacity, 900 MW]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: projectCapacity Context triple: [Arun III Hydroelectric Project, projectCapacity, 900 MW]
-
A.
productionCapacity
Indicates the maximum amount of output an entity can produce within a given time or resource constraint.
-
B.
operatorCapacity
Indicates the maximum workload or volume of tasks that an operator is able to handle within a given context or time frame.
-
C.
hasPlannedCapacity
chosen
Indicates that an entity is associated with a specified capacity level that is planned or intended for future use rather than currently realized.
-
D.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
E.
annualCapacity
Indicates the maximum amount of output or throughput an entity can produce or handle within a one-year period.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.