Triple
T25081949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajah of Sarawak |
E628208
|
entity |
| Predicate | ethnicBackgroundOfDynasty |
P100586
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [Rajah of Sarawak, ethnicBackgroundOfDynasty, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicBackgroundOfDynasty Context triple: [Rajah of Sarawak, ethnicBackgroundOfDynasty, British]
-
A.
dynasticOrigin
Indicates the historical dynasty or ruling family from which an entity originates or descends.
-
B.
dynasticEthnicity
chosen
Indicates the ethnic or cultural lineage associated with a particular dynasty or ruling house.
-
C.
regentDynasty
Indicates that one entity served as the ruling dynasty or regent house governing on behalf of another entity (such as a realm, monarch, or territory).
-
D.
formedDynasty
Indicates that an entity established or created a ruling dynasty.
-
E.
belongsToDynasticHistory
Indicates that something is part of, or associated with, a particular dynastic historical period or lineage.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 18, 2026, 6:22 a.m.