Triple
T25082227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooke dynasty |
E628214
|
entity |
| Predicate | postDynastyMovement |
P157620
|
FINISHED |
| Object | anti-cession movement in Sarawak |
—
|
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: anti-cession movement in Sarawak | Statement: [Brooke dynasty, postDynastyMovement, anti-cession movement in Sarawak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postDynastyMovement Context triple: [Brooke dynasty, postDynastyMovement, anti-cession movement in Sarawak]
-
A.
dynastyChange
Indicates a transition in ruling power from one dynasty to another.
-
B.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
-
C.
dynasty
Indicates a hereditary ruling line or family that holds power over a state or territory across successive generations.
-
D.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
-
E.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461df9e5c8190a7718943b8b1400f |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:22 a.m.