Triple
T31687913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Jamalullail |
E808710
|
entity |
| Predicate | traditionalRulersOf |
P108031
|
FINISHED |
| Object | Perlis |
—
|
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: Perlis | Statement: [House of Jamalullail, traditionalRulersOf, Perlis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalRulersOf Context triple: [House of Jamalullail, traditionalRulersOf, Perlis]
-
A.
coRulership
Indicates a relationship in which two or more entities share authority or power to rule jointly over the same domain or group.
-
B.
historicalRulers
Indicates that one entity has served as a ruler or governing authority over the other entity at some point in history.
-
C.
recognizedAsRulersBy
Indicates that certain entities are acknowledged or accepted by others as their legitimate rulers or authorities.
-
D.
hasTraditionalRulers
chosen
Indicates that one entity possesses or is governed by traditional rulers associated with it.
-
E.
rulingDynasties
Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 30, 2026, 11:07 p.m.