Triple
T25587213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bank of Madras |
E641417
|
entity |
| Predicate | indirectSuccessor |
P11447
|
FINISHED |
| Object | State Bank of India |
—
|
NE NERFINISHED |
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: State Bank of India | Statement: [Bank of Madras, indirectSuccessor, State Bank of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indirectSuccessor Context triple: [Bank of Madras, indirectSuccessor, State Bank of India]
-
A.
successorDeterminedBy
Indicates that the identity of a successor is established or chosen according to a specified rule, process, or determining factor.
-
B.
successorInLineage
Indicates that one entity is the next direct descendant or inheritor in a genealogical or hierarchical lineage from another entity.
-
C.
eventualSuccessor
chosen
Indicates that one entity will become the successor of another at some later point in time, rather than immediately.
-
D.
successorUsedIn
Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
-
E.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
- 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_69e75dc42b588190a98b58e0df359674 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f96a44bc8190a38439dbc297ebc5 |
completed | May 2, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:17 p.m.