Triple
T14125247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Sigismund, Elector of Brandenburg |
E340012
|
entity |
| Predicate | startOfReignAsDukeOfPrussia |
P112904
|
FINISHED |
| Object | 1618 |
—
|
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: 1618 | Statement: [John Sigismund, Elector of Brandenburg, startOfReignAsDukeOfPrussia, 1618]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfReignAsDukeOfPrussia Context triple: [John Sigismund, Elector of Brandenburg, startOfReignAsDukeOfPrussia, 1618]
-
A.
startOfKingshipInPrussia
Indicates the point in time when an entity begins its reign or kingship in Prussia.
-
B.
reignAsGrandDukeOfLithuaniaStart
Indicates the time at which an individual begins their tenure as Grand Duke of Lithuania.
-
C.
reignAsDukeOfSaxonyStart
Indicates the time at which an individual begins their tenure ruling in the position of Duke of Saxony.
-
D.
reignAsKingOfGermanyStart
Indicates the time point or event at which an individual begins their reign as King of Germany.
-
E.
reignAsDukeOfBavariaFrom
Indicates that a person held and exercised the title and authority of Duke of Bavaria starting from a specified time.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6096976481909dc79066c5165a50 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:22 p.m.