Triple
T21142827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gujarat princely states |
E520974
|
entity |
| Predicate | rulersHeldTitle |
P10605
|
FINISHED |
| Object | Maharaja |
—
|
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: Maharaja | Statement: [Gujarat princely states, rulersHeldTitle, Maharaja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulersHeldTitle Context triple: [Gujarat princely states, rulersHeldTitle, Maharaja]
-
A.
titleHeldByRulers
chosen
Indicates that a specific title is or was borne by one or more rulers.
-
B.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
C.
successorTitleHolders
Indicates that one entity holds a title immediately after another entity, as the successor in that title-holding sequence.
-
D.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
E.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723fad02c8190a8e9fb82f0491642 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.