Triple
T25373498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fürst von Bismarck |
E632992
|
entity |
| Predicate | statusAfter1919 |
P164983
|
FINISHED |
| Object | legally abolished as privilege in Germany |
—
|
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: legally abolished as privilege in Germany | Statement: [Fürst von Bismarck, statusAfter1919, legally abolished as privilege in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1919 Context triple: [Fürst von Bismarck, statusAfter1919, legally abolished as privilege in Germany]
-
A.
statusAfter1910
Indicates the status or condition of an entity as it exists after the year 1910.
-
B.
statusAfter1918
Indicates the status or condition of an entity as it existed after the year 1918.
-
C.
statusAfter1917
Indicates the condition or state of an entity as it existed after the year 1917, typically in contrast to its prior status.
-
D.
statusBefore1918
Indicates that a particular status, condition, or classification applied to an entity prior to the year 1918.
-
E.
statusAfter1869
Indicates the status or condition an entity has at some point after the year 1869.
- F. None of above. chosen
Provenance (4 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 21, 2026, 1:38 p.m.