Triple
T17307287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cis-Sutlej states |
E420194
|
entity |
| Predicate | rulerTitleCommonly |
P17756
|
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: [Cis-Sutlej states, rulerTitleCommonly, Maharaja]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulerTitleCommonly Context triple: [Cis-Sutlej states, rulerTitleCommonly, Maharaja]
-
A.
traditionalRulerTitleInArea
Indicates that a specific traditional ruler’s title is officially recognized as holding authority within a particular geographic or administrative area.
-
B.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
C.
hasRulerTitle
chosen
Indicates that a ruler holds or is associated with a specific formal title of rulership.
-
D.
titleHolderRuled
Indicates that the entity holding a particular title exercised ruling authority or governance over another entity or domain.
-
E.
mainRuler
Indicates that one entity is the primary sovereign or highest-ranking ruler over another entity, such as a territory, people, or political unit.
- 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4390005dc81908345ebb6dd970582 |
completed | April 19, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.