Triple
T22230468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Rome |
E549451
|
entity |
| Predicate | nativeLabel |
P657
|
FINISHED |
| Object | Rex Romanorum |
—
|
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: Rex Romanorum | Statement: [King of Rome, nativeLabel, Rex Romanorum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rex Romanorum Context triple: [King of Rome, nativeLabel, Rex Romanorum]
-
A.
Rex Romanorum
chosen
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.
-
B.
Rex Francorum
Rex Francorum is the Latin royal title meaning "King of the Franks," historically used by rulers of the Frankish realms in medieval Europe.
-
C.
Romanus
Romanus is a Latin masculine given name and cognomen historically used throughout the Roman world and later in various European cultures.
-
D.
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.
-
E.
Rex Italiae
Rex Italiae is the Latin title historically used to designate the King of Italy in various periods of the Italian peninsula’s monarchy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf2a26c81908aaf614d7c75e219 |
completed | April 28, 2026, 9:51 p.m. |
Created at: April 16, 2026, 8:37 p.m.