Triple
T31197661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princeps Pedemontii |
E795364
|
entity |
| Predicate | successorTitleInKingdomOfItaly |
P198341
|
FINISHED |
| Object | Prince of Piedmont |
—
|
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: Prince of Piedmont | Statement: [Princeps Pedemontii, successorTitleInKingdomOfItaly, Prince of Piedmont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorTitleInKingdomOfItaly Context triple: [Princeps Pedemontii, successorTitleInKingdomOfItaly, Prince of Piedmont]
-
A.
successorAsKingOfItaly
Indicates that one person became the next king of Italy after another person.
-
B.
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.
-
C.
successorAsKingOfNaples
Indicates that one person became the next king of Naples following another person’s reign.
-
D.
reignAsKingOfItalyEnd
Indicates the point in time or event at which an individual's reign as King of Italy comes to an end.
-
E.
successorAsGrandDukeOfTuscany
Indicates the person who directly followed another as the Grand Duke of Tuscany in the line of succession.
- F. None of above. chosen
Provenance (4 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
| PDg | Predicate description generation | batch_69fedec5e1708190a0b13be7533d55d8 |
completed | May 9, 2026, 7:14 a.m. |
Created at: April 29, 2026, 9:09 p.m.