Triple
T2525982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oude |
E56035
|
entity |
| Predicate | statusUnderBritishRule |
P6044
|
FINISHED |
| Object | princely state |
—
|
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: princely state | Statement: [Oude, statusUnderBritishRule, princely state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusUnderBritishRule Context triple: [Oude, statusUnderBritishRule, princely state]
-
A.
capitalDuringBritishRule
Indicates that a place served as the capital of a region or polity specifically during the period of British rule.
-
B.
broughtUnderBritishCrown
chosen
Indicates that an entity was placed under the authority, control, or sovereignty of the British Crown.
-
C.
periodOfColonialRule
Indicates the time span during which one political power exercised colonial control over another territory or people.
-
D.
viewOnBritishRule
Indicates a person or group's attitude, opinion, or stance toward British colonial rule.
-
E.
usedByColonialPower
Indicates that something is employed or exploited as a tool, resource, or mechanism by a colonial power in the context of domination or control.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2544b4481908e105294cebdbb1f |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.