Triple
T13098606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raja |
E310655
|
entity |
| Predicate | statusUnderBritishRaj |
P106914
|
FINISHED |
| Object | recognized princely title |
—
|
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: recognized princely title | Statement: [Raja, statusUnderBritishRaj, recognized princely title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusUnderBritishRaj Context triple: [Raja, statusUnderBritishRaj, recognized princely title]
-
A.
underColonialRuleBy
Indicates that one entity was governed, controlled, or dominated as a colony by another political power.
-
B.
capitalDuringBritishRule
Indicates that a place served as the capital of a region or polity specifically during the period of British rule.
-
C.
endTimeAsCapitalOfBritishIndia
Indicates the point in time when a location ceased to serve as the capital of British India.
-
D.
administrativeStatusUnderBritish
chosen
Indicates the type or condition of an entity’s administrative relationship or governance status under British authority.
-
E.
laterCapitalDuringBritishRule
Indicates that one entity served as the capital of the other at a later period specifically during British rule.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d981500d34819097037b3c3c33627b |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:04 p.m.