Triple
T31985446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bavarian Senate |
E816708
|
entity |
| Predicate | abolitionApprovedBy |
P60723
|
FINISHED |
| Object | Bavarian voters |
—
|
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: Bavarian voters | Statement: [Bavarian Senate, abolitionApprovedBy, Bavarian voters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolitionApprovedBy Context triple: [Bavarian Senate, abolitionApprovedBy, Bavarian voters]
-
A.
finalAbolition
Indicates the complete and permanent elimination of something, such that it no longer exists or is practiced in any form.
-
B.
statuteApprovedBy
chosen
Indicates that a statute has received formal approval or authorization from a specified person, body, or authority.
-
C.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
-
D.
rankAbolished
Indicates that a particular rank, title, or position has been officially discontinued or removed from use.
-
E.
permitsAbolitionOf
Indicates that one entity authorizes or allows the elimination, repeal, or discontinuation of another entity, condition, or practice.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b1045081908ba99d7a84d03649 |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:12 a.m.