Triple
T32980116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raja Ashman Shah |
E843772
|
entity |
| Predicate | monarchInHouseOf |
P131768
|
FINISHED |
| Object | Sultanate of Perak |
—
|
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 Perak | Statement: [Raja Ashman Shah, monarchInHouseOf, Sultanate of Perak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchInHouseOf Context triple: [Raja Ashman Shah, monarchInHouseOf, Sultanate of Perak]
-
A.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
B.
monarchInFamily
Indicates that a member of a family holds (or held) the position of monarch within that family lineage.
-
C.
monarchIs
Indicates that one entity serves as the ruling monarch (such as king, queen, or equivalent sovereign) of another entity, typically a state or territory.
-
D.
crownedMonarchHouse
Indicates that a particular royal house is the one from which a given monarch was crowned or to which that crowned monarch belongs.
-
E.
monarchicalHouse
chosen
Indicates that an entity belongs to, is associated with, or is part of a particular royal or monarchical house or dynasty.
- 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:22 a.m.