Triple
T30138400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathan dynasty |
E766060
|
entity |
| Predicate | hasTypeOfMonarch |
P21959
|
FINISHED |
| Object | Nawab of Tonk |
—
|
NE NERFINISHED |
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: Nawab of Tonk | Statement: [Pathan dynasty, hasTypeOfMonarch, Nawab of Tonk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfMonarch Context triple: [Pathan dynasty, hasTypeOfMonarch, Nawab of Tonk]
-
A.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
B.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
C.
hasMonarchicalOrder
Indicates that there exists a hierarchical structure of authority organized according to monarchical principles (e.g., ranks, succession, or rule by a monarch).
-
D.
hasTypeOfRuler
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
E.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 29, 2026, 7:17 p.m.