Triple
T9021086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manikya dynasty |
E215723
|
entity |
| Predicate | mergerInstrument |
P38070
|
FINISHED |
| Object | Instrument of Accession |
—
|
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: Instrument of Accession | Statement: [Manikya dynasty, mergerInstrument, Instrument of Accession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerInstrument Context triple: [Manikya dynasty, mergerInstrument, Instrument of Accession]
-
A.
institutionalMergerInstrument
chosen
Indicates that a particular legal or formal instrument is used as the means or mechanism by which two or more institutions are merged.
-
B.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
C.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
D.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
-
E.
mergerSettlement
Indicates a legal or financial resolution reached between parties involved in a merger, typically settling disputes or claims arising from the merger transaction.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a43add08190983b7ac88576fd7e |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.