Triple
T26010784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry VI |
E646892
|
entity |
| Predicate | predecessor as King of Sicily |
P36571
|
FINISHED |
| Object | Tancred of Lecce |
—
|
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: Tancred of Lecce | Statement: [Henry VI, predecessor as King of Sicily, Tancred of Lecce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessor as King of Sicily Context triple: [Henry VI, predecessor as King of Sicily, Tancred of Lecce]
-
A.
predecessorAsKingOfSicily
chosen
Indicates that one entity previously held the position of King of Sicily immediately before another entity.
-
B.
predecessorAsKingOfNaples
Indicates that one entity served as the immediately preceding king of Naples relative to another entity.
-
C.
successorAsKingOfSicily
Indicates that one person became the next king of Sicily after another person.
-
D.
successorAsKingOfNaples
Indicates that one person became the next king of Naples following another person’s reign.
-
E.
predecessorAsKingOfItaly
Indicates that one entity previously held the position of King of Italy immediately before another entity, establishing a direct succession in that royal office.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 22, 2026, 9:01 a.m.