Triple
T24077072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August III Sas |
E596393
|
entity |
| Predicate | electorateReignStart |
P1506
|
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: [August III Sas, electorateReignStart, 1733]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electorateReignStart Context triple: [August III Sas, electorateReignStart, 1733]
-
A.
inauguratedReignOf
Indicates that one entity formally began or initiated the period of rule or reign of another entity.
-
B.
electorateEstablishedFor
Indicates that a particular electorate or voting district has been created or designated to serve and represent a specific entity (such as a body, office, or jurisdiction).
-
C.
electorateEstablished
Indicates that an electorate or voting district has been formally created or brought into existence.
-
D.
electorateEstablishedBy
Indicates that an electorate (voting district or body of voters) was created or formally brought into existence by a specific authority, law, or founding action.
-
E.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
- 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_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. |
Created at: April 17, 2026, 10:42 p.m.