Triple
T16514605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian princes |
E401148
|
entity |
| Predicate | lostRulingPowersOn |
P76678
|
FINISHED |
| Object | 15 August 1947 |
—
|
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: 15 August 1947 | Statement: [Indian princes, lostRulingPowersOn, 15 August 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostRulingPowersOn Context triple: [Indian princes, lostRulingPowersOn, 15 August 1947]
-
A.
lostSovereigntyIn
Indicates that an entity ceased to possess or exercise sovereign authority within a specified place or domain.
-
B.
lostSovereignty
chosen
Indicates that an entity has ceased to possess independent authority or control over its own governance or territory.
-
C.
lostMostPowersTo
Indicates that one entity has been deprived of the majority of its powers, abilities, or authority as a result of another entity’s actions or influence.
-
D.
lostAdministrativePrimacyTo
Indicates that one entity ceased to be the primary administrative authority and that this leading administrative role was transferred to another entity.
-
E.
lostMonopolyOnPower
Indicates that an entity previously held exclusive control or authority but no longer maintains that sole dominance.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7a5ff88190984e2f2bc2fd17cc |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.