Triple
T22632016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Prussia |
E558576
|
entity |
| Predicate | yearBecameCoreOfGermanEmpire |
P149005
|
FINISHED |
| Object | 1871 |
—
|
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: 1871 | Statement: [Kingdom of Prussia, yearBecameCoreOfGermanEmpire, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearBecameCoreOfGermanEmpire Context triple: [Kingdom of Prussia, yearBecameCoreOfGermanEmpire, 1871]
-
A.
acquiredByWilhelmII
Indicates that something was obtained, taken over, or brought under the ownership or control of Wilhelm II.
-
B.
startOfRuleOverGermanEmpire
Indicates the point in time when governance or dominion over the German Empire begins for a particular ruler or ruling authority.
-
C.
statusDuringGermanEmpire
Indicates the status or condition an entity held specifically during the period of the German Empire.
-
D.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
E.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17009ecb0819082f94505b0e2c5b8 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:02 p.m.