Triple
T10408252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanisław Leszczyński |
E245320
|
entity |
| Predicate | duchyReignEnd |
P64974
|
FINISHED |
| Object | 1766 |
—
|
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: 1766 | Statement: [Stanisław Leszczyński, duchyReignEnd, 1766]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duchyReignEnd Context triple: [Stanisław Leszczyński, duchyReignEnd, 1766]
-
A.
endOfReign
Indicates the point in time or event at which a ruler’s or leader’s period of authority or reign concludes.
-
B.
reignEndAsDukeOfNormandy
Indicates the time or event at which an individual's rule or authority as Duke of Normandy comes to an end.
-
C.
reignAsDukeOfBrittanyEnd
chosen
Indicates the point in time or event at which an individual's tenure or rule as Duke of Brittany comes to an end.
-
D.
dynastyEndedWith
Indicates that a particular dynasty concluded or came to an end with the specified ruler, event, or time period.
-
E.
duchyFoundedBy
Indicates that a particular duchy was established or created by a specific person, group, or authority.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9f9b59881909797646fd8cd6a7e |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:09 p.m.