Triple
T26400363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Sikkim |
E663679
|
entity |
| Predicate | joinedIndiaAs |
P99767
|
FINISHED |
| Object | 22nd state of India |
—
|
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: 22nd state of India | Statement: [Kingdom of Sikkim, joinedIndiaAs, 22nd state of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedIndiaAs Context triple: [Kingdom of Sikkim, joinedIndiaAs, 22nd state of India]
-
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.
joinedNorthernUnion
Indicates that an entity became a member of, or formally aligned with, the Northern Union.
-
C.
joinedIndependentState
Indicates that an entity became a member of an independent state, typically by formally joining or being incorporated into that sovereign political unit.
-
D.
admittedToIndianUnionAsPartBStateOn
Indicates that an entity was incorporated into the Indian Union as a Part B state on a specified date.
-
E.
joinedAsProvince
Indicates that an entity became part of a larger political or administrative unit with the status of a province.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 11:31 p.m.