Triple
T13226890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court party |
E314904
|
entity |
| Predicate | typeOfMonarchySupported |
P21959
|
FINISHED |
| Object | hereditary monarchy |
—
|
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: hereditary monarchy | Statement: [Court party, typeOfMonarchySupported, hereditary monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfMonarchySupported Context triple: [Court party, typeOfMonarchySupported, hereditary monarchy]
-
A.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
B.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
C.
typeOfMonarchyUntil1979
Indicates the specific form of monarchy that governed an entity up to, but not beyond, the year 1979.
-
D.
constitutionalMonarchyEstablished
Indicates that a constitutional monarchy as a system of government has been formally created or brought into existence.
-
E.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.