Triple
T7219078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Emperor |
E150209
|
entity |
| Predicate | legalStatusAfter1918 |
P32617
|
FINISHED |
| Object | abolished with German Revolution of 1918–1919 |
—
|
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: abolished with German Revolution of 1918–1919 | Statement: [German Emperor, legalStatusAfter1918, abolished with German Revolution of 1918–1919]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfter1918 Context triple: [German Emperor, legalStatusAfter1918, abolished with German Revolution of 1918–1919]
-
A.
legalStatusAfter1919
Indicates the legal status or condition of an entity as it existed after the year 1919.
-
B.
legalStatusAfter1917
Indicates the legal status or condition of an entity as it existed after the year 1917.
-
C.
statusAfter1918
chosen
Indicates the status or condition of an entity as it existed after the year 1918.
-
D.
legalStatusAfterWar
Indicates the legal condition or classification assigned to an entity as a consequence of, or following the conclusion of, a war or armed conflict.
-
E.
legalStatusBefore1889
Indicates the legal status or condition that applied to an entity prior to the year 1889.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b045c48190b27b2d6f7c11026f |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.