Triple
T6444376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union of India |
E138303
|
entity |
| Predicate | hasSovereignPowerOver |
P70686
|
FINISHED |
| Object | states 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: states of India | Statement: [Union of India, hasSovereignPowerOver, states of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereignPowerOver Context triple: [Union of India, hasSovereignPowerOver, states of India]
-
A.
hasSovereignState
Indicates that one entity is the sovereign state that has ultimate authority or jurisdiction over another entity.
-
B.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
C.
sovereigntyRegime
Indicates the type or structure of political authority and control exercised over a territory or population.
-
D.
sovereigntyBasedOn
Indicates that one entity’s sovereignty or governing authority is derived from, justified by, or contingent upon another specified basis or source.
-
E.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
- F. None of above. chosen
Provenance (4 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698c17ec81909f6bbcbe636a67fd |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.