Triple
T16152807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsar of Bulgaria |
E391956
|
entity |
| Predicate | monarchicForm |
P21959
|
FINISHED |
| Object | constitutional 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: constitutional monarchy | Statement: [Tsar of Bulgaria, monarchicForm, constitutional monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchicForm Context triple: [Tsar of Bulgaria, monarchicForm, constitutional monarchy]
-
A.
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.
-
B.
monarchicContext
Indicates that the relationship or action occurs within, is shaped by, or pertains to a monarchical system of rule or authority.
-
C.
traditionalMonarchy
Indicates a system where a monarchy operates according to long-established customs, hereditary succession, and historical institutions rather than modern or codified reforms.
-
D.
monarch
Indicates that an entity serves as the sovereign ruler (such as a king, queen, or emperor) over a state or territory.
-
E.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d98d08c8190a15d4aee40d47220 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:01 a.m.