Triple
T8065115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priyadarshini Jurala Dam |
E188223
|
entity |
| Predicate | commissioningYear |
P2009
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Priyadarshini Jurala Dam, commissioningYear, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commissioningYear Context triple: [Priyadarshini Jurala Dam, commissioningYear, 1995]
-
A.
commissionedYear
chosen
Indicates the year in which something (typically a work, project, or item) was formally ordered, authorized, or put into production.
-
B.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
C.
compilationYear
Indicates the year in which a work, collection, or set of materials was compiled or assembled into its final form.
-
D.
incorporationYear
Indicates the calendar year in which an organization or entity was formally incorporated or legally established.
-
E.
regulatoryApprovalYear
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ff5547c8190a7ec5958a23e302f |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:26 p.m.