Triple
T29897207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratan Tata |
E759310
|
entity |
| Predicate | reinstatementEndTime |
P109066
|
FINISHED |
| Object | 2017-01 |
—
|
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: 2017-01 | Statement: [Ratan Tata, reinstatementEndTime, 2017-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reinstatementEndTime Context triple: [Ratan Tata, reinstatementEndTime, 2017-01]
-
A.
revivalEndTime
chosen
Indicates the point in time at which a revival process, event, or restored state comes to an end.
-
B.
renewalDate
Indicates the date on which an existing agreement, subscription, or arrangement is scheduled to be renewed or extended.
-
C.
laterRenewedFor
Indicates that an existing agreement, contract, or arrangement was renewed again at a subsequent, later time.
-
D.
reauthorizationPeriodStart
Indicates the point in time when a new or renewed authorization period begins.
-
E.
reauthorizedIn
Indicates that an existing authorization, agreement, or mandate was renewed or granted again at a specific time or in a specific context.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6772c7cc48190b2a3616b9fdcb7e4 |
completed | May 2, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:05 p.m.