Triple
T32993868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maharawal |
E844166
|
entity |
| Predicate | administrativeAreaRuled |
P194195
|
FINISHED |
| Object | Dungarpur region |
—
|
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: Dungarpur region | Statement: [Maharawal, administrativeAreaRuled, Dungarpur region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeAreaRuled Context triple: [Maharawal, administrativeAreaRuled, Dungarpur region]
-
A.
historicalRegionGoverned
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
B.
ruledUnderPolity
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
C.
laterGovernedAs
Indicates that an entity subsequently held governing authority over another entity at a later time.
-
D.
countryRuled
Indicates that one entity exercises governing authority or political control over a country.
-
E.
historicallyUnderRuleOf
Indicates that one entity was historically governed, controlled, or ruled by another entity during a past period.
- F. None of above. chosen
Provenance (4 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
| PDg | Predicate description generation | batch_69fd67182c348190aa84a02e08dbf4e1 |
completed | May 8, 2026, 4:31 a.m. |
Created at: May 1, 2026, 1:22 a.m.