Triple
T30412983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharaja of Tripura |
E773670
|
entity |
| Predicate | mergerDateWithIndia |
P99767
|
FINISHED |
| Object | 1949-09-09 |
—
|
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: 1949-09-09 | Statement: [Maharaja of Tripura, mergerDateWithIndia, 1949-09-09]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerDateWithIndia Context triple: [Maharaja of Tripura, mergerDateWithIndia, 1949-09-09]
-
A.
integratedIntoIndianUnionAs
chosen
Indicates that an entity (such as a region or princely state) was formally incorporated into the political and administrative framework of the Indian Union.
-
B.
establishedAsUnionTerritoryOn
Indicates the date or event on which a region was formally designated and constituted as a union territory.
-
C.
governedIndiaUntil
Indicates that a subject held governing authority over India up to a specified end time or date.
-
D.
admittedToIndianUnionAsPartBStateOn
Indicates that an entity was incorporated into the Indian Union as a Part B state on a specified date.
-
E.
mergerWithKhyberPakhtunkhwaDate
Indicates the date on which an entity merged with the Khyber Pakhtunkhwa region or administrative unit.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686478d64819084a68bcd9c02bd8a |
completed | May 2, 2026, 11:18 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:05 p.m.