Triple
T6970012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Bank of India |
E161575
|
entity |
| Predicate | nationalizedIn |
P18594
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [Imperial Bank of India, nationalizedIn, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalizedIn Context triple: [Imperial Bank of India, nationalizedIn, 1955]
-
A.
nationalised
Indicates that control or ownership of an entity has been transferred from private or non-state hands to the government or state.
-
B.
nationalisedOn
Indicates the date or point in time when an entity was taken into state ownership or control by a national government.
-
C.
nationalisationYear
chosen
Indicates the year in which an entity was taken into state ownership or control through nationalisation.
-
D.
typeOfNationalisation
Indicates the specific form or method by which an asset, industry, or entity is brought under national or state ownership or control.
-
E.
region after nationalisation
Indicates that a region is characterized or defined by its status or condition following a process of nationalisation.
- 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1649288190a52c7dab57b3c7dc |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.