Triple
T31719806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sultan Mahmud Shah III |
E809541
|
entity |
| Predicate | providedRulersFor |
P78587
|
FINISHED |
| Object | Sultanate of Johor |
—
|
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: Sultanate of Johor | Statement: [House of Sultan Mahmud Shah III, providedRulersFor, Sultanate of Johor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providedRulersFor Context triple: [House of Sultan Mahmud Shah III, providedRulersFor, Sultanate of Johor]
-
A.
providedRulerFor
chosen
Indicates that one entity supplied or designated another entity to serve as the ruler or governing authority over a particular domain or group.
-
B.
usedByRuler
Indicates that something is employed, utilized, or otherwise put to use by a ruler or governing authority.
-
C.
targetedRuler
Indicates that an entity intentionally directed hostile or coercive actions specifically against a ruling individual or authority figure.
-
D.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
-
E.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 30, 2026, 11:18 p.m.