Triple
T25258869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yantra India Limited |
E633247
|
entity |
| Predicate | corporatizationProgram |
P4439
|
FINISHED |
| Object | OFB corporatization 2021 |
—
|
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: OFB corporatization 2021 | Statement: [Yantra India Limited, corporatizationProgram, OFB corporatization 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: corporatizationProgram Context triple: [Yantra India Limited, corporatizationProgram, OFB corporatization 2021]
-
A.
companyProgram
Indicates that a program is organized, operated, or sponsored by a specific company.
-
B.
corporateTransformation
chosen
Indicates a relationship where an organization undergoes a significant structural, strategic, or operational change from one corporate state to another.
-
C.
rebrandingProgram
Indicates a program or initiative through which an entity changes or updates its brand identity, such as its name, logo, or overall image.
-
D.
agencyProgramme
Indicates that an agency is responsible for, manages, or is associated with a particular programme.
-
E.
adoptedProgramme
Indicates that an entity has formally accepted and put into practice a specific programme or plan.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f483904578819096518f6a0a82a31f |
completed | May 1, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:13 p.m.