Triple
T32839745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tungabhadra Hydroelectric Project |
E839928
|
entity |
| Predicate | isMultipurposeProject |
P20608
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tungabhadra Hydroelectric Project, isMultipurposeProject, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMultipurposeProject Context triple: [Tungabhadra Hydroelectric Project, isMultipurposeProject, true]
-
A.
isMultiPurpose
chosen
Indicates that something is designed or used to serve multiple functions or purposes rather than a single, specialized one.
-
B.
isOneOffProject
Indicates that the project is a unique, non-recurring effort rather than part of an ongoing or repeated series of projects.
-
C.
isMultidisciplinary
Indicates that something involves or integrates multiple distinct academic or professional disciplines in its approach or composition.
-
D.
isPublicUtilityProject
Indicates that a project is classified as a public utility initiative serving essential community or infrastructure needs.
-
E.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
- 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.