Triple
T24077050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederick Augustus |
E596392
|
entity |
| Predicate | predecessorAsElectorOfSaxony |
P154765
|
FINISHED |
| Object | Augustus II the Strong |
—
|
NE NERFINISHED |
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: Augustus II the Strong | Statement: [Frederick Augustus, predecessorAsElectorOfSaxony, Augustus II the Strong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsElectorOfSaxony Context triple: [Frederick Augustus, predecessorAsElectorOfSaxony, Augustus II the Strong]
-
A.
predecessorAsDukeOfSaxony
Indicates that one entity previously held the title of Duke of Saxony immediately before another entity.
-
B.
successorAsElectorOfSaxony
Indicates that one entity became the next holder of the title Elector of Saxony directly after another entity.
-
C.
predecessorAsKingOfPrussia
Indicates that one entity served as the immediately preceding king of Prussia relative to another entity.
-
D.
predecessorAsDukeOfPrussia
Indicates that one entity previously held the title of Duke of Prussia immediately before another entity.
-
E.
predecessorAsDukeOfSilesia
Indicates that one entity previously held the title of Duke of Silesia immediately before another entity.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1e959c81909f4365b5d7f934d9 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:42 p.m.