Triple
T32568371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Sultan Muzaffar Shah VI |
E832435
|
entity |
| Predicate | basisOfRule |
P174604
|
FINISHED |
| Object | dynastic legitimacy |
—
|
LITERAL FINISHED |
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: dynastic legitimacy | Statement: [House of Sultan Muzaffar Shah VI, basisOfRule, dynastic legitimacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfRule Context triple: [House of Sultan Muzaffar Shah VI, basisOfRule, dynastic legitimacy]
-
A.
basedOnRule
Indicates that something is determined, derived, or decided according to a specified rule or set of rules.
-
B.
natureOfRule
Indicates the fundamental type or character of a rule, specifying what kind of rule it is or how it functions within a system.
-
C.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
D.
subjectOfRule
Indicates that an entity is governed, constrained, or described by a particular rule.
-
E.
policyBasis
Indicates that one entity serves as the foundational rationale, authority, or guiding principle upon which a policy or rule is established or justified.
- F. None of above. chosen
Provenance (4 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c639039481908ea626bba7580f9e |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:03 a.m.