Triple
T33195588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mullaperiyar Dam |
E849747
|
entity |
| Predicate | leaseRenewalYear |
P149409
|
FINISHED |
| Object | 1970 |
—
|
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: 1970 | Statement: [Mullaperiyar Dam, leaseRenewalYear, 1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaseRenewalYear Context triple: [Mullaperiyar Dam, leaseRenewalYear, 1970]
-
A.
reaffirmationYear
chosen
Indicates the year in which a previously established agreement, decision, or commitment is formally confirmed or renewed.
-
B.
renewalTerm
Indicates the length or conditions of time for which an agreement, contract, or subscription is extended beyond its initial term.
-
C.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
D.
leasePeriod
Indicates the duration or time span for which a lease agreement is valid between parties.
-
E.
leaseExtendedUntil
Indicates that an existing lease agreement has been prolonged so that its validity now continues up to a specified end date.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:29 a.m.