Triple
T33246752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khandavala dynasty |
E851122
|
entity |
| Predicate | rulingClassOf |
P89474
|
FINISHED |
| Object | Maithil people |
—
|
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: Maithil people | Statement: [Khandavala dynasty, rulingClassOf, Maithil people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulingClassOf Context triple: [Khandavala dynasty, rulingClassOf, Maithil people]
-
A.
hasRulingPeople
Indicates that a group or entity serves as the governing or ruling authority over another entity.
-
B.
ethnicGroupOfRulers
Indicates the ethnic group to which the rulers of a given political or territorial entity belong or belonged.
-
C.
hadRulingClass
chosen
Indicates that a particular group or class held dominant political, economic, or social power over a society or entity.
-
D.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
E.
rulingHouse
Indicates that one entity serves as the dynastic or noble family that holds ruling authority over another entity, such as a state, territory, or polity.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6daf4ae588190b8884f67b6bc616d |
completed | May 3, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69f6d82fef788190b9ad19a36c0312dc |
completed | May 3, 2026, 5:08 a.m. |
Created at: May 1, 2026, 1:31 a.m.