Triple
T6479552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augustus III of Poland |
E146153
|
entity |
| Predicate | electionAsKingOfPoland |
P34663
|
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: [Augustus III of Poland, electionAsKingOfPoland, 1733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionAsKingOfPoland Context triple: [Augustus III of Poland, electionAsKingOfPoland, 1733]
-
A.
successorAsKingOfPoland
Indicates that one person became the next king of Poland following another person’s reign.
-
B.
reignAsKingOfPolandEnd
Indicates the time or event at which an individual’s reign as King of Poland comes to an end.
-
C.
predecessorAsKingOfPoland
Indicates that one person previously held the position of King of Poland immediately before another person.
-
D.
reignAsKingOfPolandStart
chosen
Indicates the time at which an entity begins its reign as king over Poland.
-
E.
successorInSandomierz
Indicates that one entity directly follows another as its successor in the context of Sandomierz (e.g., in an office, role, or position associated with Sandomierz).
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4e764c819086828bb841f588e0 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:51 p.m.