Triple
T3271304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hohenzollern |
E68653
|
entity |
| Predicate | startOfRuleOverGermanEmpire |
P47016
|
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: [House of Hohenzollern, startOfRuleOverGermanEmpire, 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfRuleOverGermanEmpire Context triple: [House of Hohenzollern, startOfRuleOverGermanEmpire, 1871]
-
A.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
B.
reignAsKingOfGermanyEnd
Indicates the time or event at which an individual’s tenure as king of Germany comes to an end.
-
C.
startOfUseAsSoleGermanCurrency
Indicates the point in time when something first began to be used as the only official currency in Germany.
-
D.
startDateAsGrandDuchy
Indicates the date on which an entity began its existence or status as a grand duchy.
-
E.
reignStartAsEmperorOfAustria
Indicates the date or point in time when an individual began their reign holding the title of Emperor of Austria.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff4b9dc8190b7e3da0bbffccf99 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada41d7eac8190ada4bf5f793d5c49 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.