Triple
T16203386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dagobert I |
E393259
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Rex Francorum |
E563499
|
NE 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: Rex Francorum | Statement: [Dagobert I, title, Rex Francorum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rex Francorum Context triple: [Dagobert I, title, Rex Francorum]
-
A.
Rex Francorum
chosen
Rex Francorum is the Latin royal title meaning "King of the Franks," historically used by rulers of the Frankish realms in medieval Europe.
-
B.
Rex Romanorum
Rex Romanorum was the medieval title used for the elected ruler of the Holy Roman Empire, designating him as king of the Romans and future emperor.
-
C.
Romanus
Romanus is a Latin masculine given name and cognomen historically used throughout the Roman world and later in various European cultures.
-
D.
Herennius Etruscus
Herennius Etruscus was a short-lived 3rd-century Roman emperor who ruled jointly with his father Decius before dying in battle against the Goths.
-
E.
Rex Siciliae
Rex Siciliae was the medieval Latin title used for the King of Sicily, a significant monarchic office in Southern Italy and the central Mediterranean.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2270ca18c8190a259992aed4ec072 |
completed | April 17, 2026, 12:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff130bcc8190a965d90e123d2dd9 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:03 a.m.