Triple
T26790806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis I, Holy Roman Emperor |
E670511
|
entity |
| Predicate | successorAsDukeOfLorraine |
P136743
|
FINISHED |
| Object | Stanisław Leszczyński |
—
|
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: Stanisław Leszczyński | Statement: [Francis I, Holy Roman Emperor, successorAsDukeOfLorraine, Stanisław Leszczyński]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsDukeOfLorraine Context triple: [Francis I, Holy Roman Emperor, successorAsDukeOfLorraine, Stanisław Leszczyński]
-
A.
successorAsDukeOfBurgundy
Indicates that one entity became the next Duke of Burgundy following another entity in the line of succession.
-
B.
successorAsDukeOfBrittany
Indicates that one entity became the next Duke of Brittany following another entity in the line of succession.
-
C.
successorAsDukeOfOrléans
Indicates that one entity became the next holder of the title Duke of Orléans after another entity.
-
D.
successorAsDukeOfAnjou
Indicates that one entity became the next holder of the title Duke of Anjou after another entity.
-
E.
successorAsDuke
chosen
Indicates that one person directly follows another in holding the title and position of duke.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 4:16 a.m.