Triple
T23494408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolesław I the Tall |
E571662
|
entity |
| Predicate | successorAsHighDuke |
P116108
|
FINISHED |
| Object | Mieszko III the Old |
—
|
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: Mieszko III the Old | Statement: [Bolesław I the Tall, successorAsHighDuke, Mieszko III the Old]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorAsHighDuke Context triple: [Bolesław I the Tall, successorAsHighDuke, Mieszko III the Old]
-
A.
successorAsDuke
Indicates that one person directly follows another in holding the title and position of duke.
-
B.
successorAsHighDukeOfPoland
chosen
Indicates that one entity became the next holder of the title High Duke of Poland after another entity, succeeding them in that position.
-
C.
successorAsDukeOfAlba
Indicates that one entity became the next holder of the title "Duke of Alba" after another entity, succeeding them in that ducal position.
-
D.
successorAsDukeOfNassau
Indicates that one person became the next Duke of Nassau following another person in that title.
-
E.
predecessorAsDuke
Indicates that one individual previously held the title of duke immediately before another individual in a succession.
- 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_69e245b4829881909b77a70e942bbd54 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7def8ac8190ade511299078d55b |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:05 p.m.