Triple
T8877465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonk State |
E211322
|
entity |
| Predicate | becameBritishProtectorate |
P84212
|
FINISHED |
| Object | 1817 |
—
|
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: 1817 | Statement: [Tonk State, becameBritishProtectorate, 1817]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: becameBritishProtectorate Context triple: [Tonk State, becameBritishProtectorate, 1817]
-
A.
protectorateEstablishedBy
Indicates that a protectorate relationship was formally created or instituted by a particular actor or authority.
-
B.
broughtUnderBritishCrown
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
C.
protectorateProclaimedYear
chosen
Indicates the year in which a protectorate status was officially declared over an entity.
-
D.
wasUnderTrusteeshipOf
Indicates that one entity was administered, overseen, or managed under the legal or formal trusteeship authority of another entity.
-
E.
replacedByAsCapitalOfBritishIndia
Indicates that one entity ceased to be the capital of British India and was succeeded in that role by another entity.
- 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_69ca838e78748190934d82db3104f855 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61496870819097c55c73aca62aac |
completed | April 1, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2956788190a311c647b4da17a6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:52 p.m.