Triple
T25094025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalhoro |
E628539
|
entity |
| Predicate | ruledUnderTitle |
P116244
|
FINISHED |
| Object | Mian |
—
|
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: Mian | Statement: [Kalhoro, ruledUnderTitle, Mian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledUnderTitle Context triple: [Kalhoro, ruledUnderTitle, Mian]
-
A.
titleHolderRuled
Indicates that the entity holding a particular title exercised ruling authority or governance over another entity or domain.
-
B.
ruledUnderPolity
chosen
Indicates that an entity exercised rule or governance while being subordinate to, or within the authority framework of, a particular polity.
-
C.
laterRulerTitle
Indicates that an entity held a particular ruler title at a later point in time, after some earlier status or title.
-
D.
ruledDuringReignOf
Indicates that one entity exercised ruling authority or governance during the time period in which another entity’s reign took place.
-
E.
ruled in
Indicates that an authority, such as a court or judge, has made a formal decision or judgment in favor of a particular party or position.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b77f94819086b73037950546fc |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:24 a.m.