Triple
T3271303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Hohenzollern |
E68653
|
entity |
| Predicate | startOfKingshipInPrussia |
P47015
|
FINISHED |
| Object | 1701 |
—
|
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: 1701 | Statement: [House of Hohenzollern, startOfKingshipInPrussia, 1701]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfKingshipInPrussia Context triple: [House of Hohenzollern, startOfKingshipInPrussia, 1701]
-
A.
reignAsKingOfPolandStart
Indicates the time at which an entity begins its reign as king over Poland.
-
B.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
C.
reignAsKingOfPolandEnd
Indicates the time or event at which an individual’s reign as King of Poland comes to an end.
-
D.
startDateAsGrandDuchy
Indicates the date on which an entity began its existence or status as a grand duchy.
-
E.
mainOpponentOfPrussia
Indicates that one entity serves as the primary adversary or principal opposing force to Prussia in a given conflict or rivalry.
- 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.