Triple
T1905552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Succession to the Crown Act 2013 |
E37794
|
entity |
| Predicate | changesRule |
P19084
|
FINISHED |
| Object | male-preference primogeniture |
—
|
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: male-preference primogeniture | Statement: [Succession to the Crown Act 2013, changesRule, male-preference primogeniture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changesRule Context triple: [Succession to the Crown Act 2013, changesRule, male-preference primogeniture]
-
A.
typicalRuleModification
Indicates a change made to a standard or default rule, adjusting how that rule normally applies or operates.
-
B.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
notableRuleChange
chosen
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
E.
cutRule
Indicates that one entity applies or enforces a rule that removes, prunes, or eliminates certain elements or possibilities from consideration.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.