Triple
T35135040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chota Nagpur princely states |
E1014546
|
entity |
| Predicate | overlordshipType |
P155300
|
FINISHED |
| Object | indirect rule |
—
|
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: indirect rule | Statement: [Chota Nagpur princely states, overlordshipType, indirect rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlordshipType Context triple: [Chota Nagpur princely states, overlordshipType, indirect rule]
-
A.
typeOfOverlordship
chosen
Indicates a hierarchical relationship in which one entity holds overlordship, or superior controlling authority, over another.
-
B.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
C.
overlordDuringReign
Indicates that one entity served as the ruling overlord of another entity during a specified reign period.
-
D.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
E.
overkingdomOf
Indicates that one kingdom holds overarching authority or sovereignty over another kingdom.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c712e58819088ee5addaf7a9d3e |
completed | May 3, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69f78b9106008190930b3b3675b737d6 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.