Triple
T26190605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Augustus II, Elector of Saxony |
E654950
|
entity |
| Predicate | electedKingOfPoland |
P178260
|
FINISHED |
| Object | 1733 |
—
|
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: 1733 | Statement: [Frederick Augustus II, Elector of Saxony, electedKingOfPoland, 1733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electedKingOfPoland Context triple: [Frederick Augustus II, Elector of Saxony, electedKingOfPoland, 1733]
-
A.
PolishKing
Indicates that the subject is a king of Poland.
-
B.
successorAsKingOfPoland
Indicates that one person became the next king of Poland following another person’s reign.
-
C.
reignAsKingOfPolandEnd
Indicates the time or event at which an individual’s reign as King of Poland comes to an end.
-
D.
coronationAsKingOfPoland
Indicates the event or relationship in which an individual is formally crowned and recognized as the King of Poland.
-
E.
predecessorAsKingOfPoland
Indicates that one person previously held the position of King of Poland immediately before another person.
- 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 26, 2026, 8:44 p.m.