Triple
T7311960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian constitutional monarchy |
E168110
|
entity |
| Predicate | crisisPower |
P76241
|
FINISHED |
| Object | reserve powers of the Crown |
—
|
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: reserve powers of the Crown | Statement: [Australian constitutional monarchy, crisisPower, reserve powers of the Crown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crisisPower Context triple: [Australian constitutional monarchy, crisisPower, reserve powers of the Crown]
-
A.
crisisRelatedTo
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
-
B.
crisisContext
Indicates that the relationship or action occurs within, is shaped by, or is specifically relevant to a crisis situation or emergency context.
-
C.
subsequentCrisis
Indicates that one crisis occurs after and as a consequence or continuation of another earlier crisis.
-
D.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
E.
emergencyPower
Indicates that an entity has backup or auxiliary power available or activated for use during emergencies or primary power failures.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ec00fef081909cb9768a70cabd80 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:02 p.m.