Triple
T6629637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Union |
E149888
|
entity |
| Predicate | sovereigntyVestedIn |
P1002
|
FINISHED |
| Object | people 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: people of India | Statement: [The Union, sovereigntyVestedIn, people of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovereigntyVestedIn Context triple: [The Union, sovereigntyVestedIn, people of India]
-
A.
seatOfSovereignty
Indicates that a location serves as the primary center of governing authority or ruling power for a political entity.
-
B.
sovereigntyStatus
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
-
C.
sovereignGovernment
Indicates that a government possesses ultimate authority and independence over a defined territory, free from external control.
-
D.
sovereigntyRegime
Indicates the type or structure of political authority and control exercised over a territory or population.
-
E.
sovereigntyBasedOn
chosen
Indicates that one entity’s sovereignty or governing authority is derived from, justified by, or contingent upon another specified basis or source.
- 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_69c687ee50048190aa151765bef16193 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6c308a08881908501c862b3029321 |
completed | March 27, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69c6ad024860819084b9b535b136ede6 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:59 p.m.