Triple
T18948545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick III, Elector of Brandenburg |
E463581
|
entity |
| Predicate | coronationDateAsKingInPrussia |
P47015
|
FINISHED |
| Object | 1701-01-18 |
—
|
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-01-18 | Statement: [Frederick III, Elector of Brandenburg, coronationDateAsKingInPrussia, 1701-01-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coronationDateAsKingInPrussia Context triple: [Frederick III, Elector of Brandenburg, coronationDateAsKingInPrussia, 1701-01-18]
-
A.
startOfReignAsDukeOfPrussia
Indicates the point in time when an individual begins their rule holding the title of Duke of Prussia.
-
B.
coronationDateAsKingOfEastFrancia
Indicates the date on which an entity was formally crowned as King of East Francia.
-
C.
coronationAsKingOfPoland
Indicates the event or relationship in which an individual is formally crowned and recognized as the King of Poland.
-
D.
startOfKingshipInPrussia
chosen
Indicates the point in time when an entity begins its reign or kingship in Prussia.
-
E.
coronationAsKingOfGermanyPlace
Indicates the place where an individual’s coronation as King of Germany took place.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d540e57c8190bb17fff6d4254320 |
completed | April 20, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon