Triple
T31339195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | His Majesty the King of Italy |
E799257
|
entity |
| Predicate | precedesNameOfMonarch |
P184614
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [His Majesty the King of Italy, precedesNameOfMonarch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesNameOfMonarch Context triple: [His Majesty the King of Italy, precedesNameOfMonarch, yes]
-
A.
precedesInReign
Indicates that one ruler’s period of reign occurred entirely before another ruler’s period of reign in a temporal succession.
-
B.
previousMonarch
Indicates that one entity served as the monarch immediately before another entity in a succession.
-
C.
predecessorThroneName
Indicates that one throne name immediately preceded another in a succession or lineage of rulership.
-
D.
precededByMonarchEra
Indicates that one monarch’s reign or era occurred immediately before another specified monarch’s era in a temporal sequence.
-
E.
reignPreceded
Indicates that one entity’s reign occurred immediately before another entity’s reign in a temporal 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 29, 2026, 9:16 p.m.