Triple
T1210401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles V, Holy Roman Emperor |
E25985
|
entity |
| Predicate | reignAsDukeOfBurgundyStart |
P1506
|
FINISHED |
| Object | 1506 |
—
|
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: 1506 | Statement: [Charles V, Holy Roman Emperor, reignAsDukeOfBurgundyStart, 1506]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignAsDukeOfBurgundyStart Context triple: [Charles V, Holy Roman Emperor, reignAsDukeOfBurgundyStart, 1506]
-
A.
reignAsDauphinFrom
Indicates the period during which a person held and exercised the title and role of Dauphin, starting from a specified time.
-
B.
reignAsDauphinTo
Indicates that one person holds and exercises the title and role of Dauphin (heir apparent to the French throne) in relation to a specific monarch or royal line.
-
C.
successorAsDukeOfNormandy
Indicates that one person becomes the next holder of the title Duke of Normandy after another person.
-
D.
reignStart
chosen
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
E.
duchyFoundedBy
Indicates that a particular duchy was established or created by a specific person, group, or authority.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bde4670481908c16a3a8c1a54aad |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.