Triple
T25795085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 16 April 1871 |
E649657
|
entity |
| Predicate | gavePrussiaSpecialRole |
P49088
|
FINISHED |
| Object | Prussian king as German Emperor |
—
|
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: Prussian king as German Emperor | Statement: [Constitution of 16 April 1871, gavePrussiaSpecialRole, Prussian king as German Emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gavePrussiaSpecialRole Context triple: [Constitution of 16 April 1871, gavePrussiaSpecialRole, Prussian king as German Emperor]
-
A.
outcomeForPrussia
Indicates the result or consequence that an event, action, or situation has specifically for Prussia.
-
B.
timeInKingdomOfPrussia
Indicates that an entity spent a specified period of time within the Kingdom of Prussia.
-
C.
associatedRulerTitlePrussia
chosen
Indicates a relationship where a ruler’s title is specifically linked to or held in connection with Prussia.
-
D.
mainOpponentOfPrussia
Indicates that one entity serves as the primary adversary or principal opposing force to Prussia in a given conflict or rivalry.
-
E.
principalNegotiatorForPrussia
Indicates that someone serves as the main representative responsible for conducting negotiations on behalf of Prussia.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5ff02f0948190b1e3cee38a97105d |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 6:28 a.m.