Triple
T31069901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ibrahim |
E791787
|
entity |
| Predicate | hasDynasticTerritory |
P86441
|
FINISHED |
| Object | Johor Sultanate |
—
|
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: Johor Sultanate | Statement: [House of Ibrahim, hasDynasticTerritory, Johor Sultanate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticTerritory Context triple: [House of Ibrahim, hasDynasticTerritory, Johor Sultanate]
-
A.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
B.
dynasticDomain
chosen
Indicates that a domain, territory, or sphere of influence is under the control or authority of a particular dynasty or ruling family.
-
C.
hasMajorDynasty
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
D.
hasDynasticSignificance
Indicates that something holds importance or influence within the context of a dynasty’s continuity, status, or historical legacy.
-
E.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:01 p.m.