Triple
T3806588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian royal family |
E93021
|
entity |
| Predicate | monarchyAbolishedBy |
P21968
|
FINISHED |
| Object | referendum in Bulgaria |
—
|
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: referendum in Bulgaria | Statement: [Bulgarian royal family, monarchyAbolishedBy, referendum in Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchyAbolishedBy Context triple: [Bulgarian royal family, monarchyAbolishedBy, referendum in Bulgaria]
-
A.
monarchyAbolishedIn
chosen
Indicates that a monarchy was officially ended or abolished in a specified place or at a specified time.
-
B.
monarchDeposed
Indicates that a monarch has been removed from power, typically against their will, by force, coercion, or formal deposition.
-
C.
endOfMonarchicalRuleInAustria
Indicates the point in time or event marking the cessation of monarchical governance in Austria.
-
D.
monarchyEstablished
Indicates that a monarchical form of government has been formally created or instituted for a given entity or territory.
-
E.
dictatorshipEndYear
Indicates the calendar year in which a particular dictatorship or dictatorial regime came to an end.
- 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_69aed96a60088190ab1df8390fffc935 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:16 p.m.