Triple
T23471586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sancho I of León |
E570142
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Rex Legionensis |
—
|
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 Legionensis | Statement: [Sancho I of León, title, Rex Legionensis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rex Legionensis Context triple: [Sancho I of León, title, Rex Legionensis]
-
A.
Rex Legionensis
chosen
Rex Legionensis is the Latin royal style meaning "King of León," historically used for monarchs such as Ordoño II of León in medieval Spain.
-
B.
Cerialis
Cerialis was a Roman general and politician of the 1st century AD, best known for his role in suppressing the Batavian revolt and serving under Emperor Vespasian.
-
C.
Rex Scottorum
Rex Scottorum is the Latin royal title meaning "King of the Scots," historically used by Scottish monarchs such as Alexander I.
-
D.
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.
-
E.
Rex Suevorum
Rex Suevorum is the Latin royal title meaning "King of the Suevi," used for rulers of the Suevic kingdom in late antiquity.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a700bd0481908047aa4678217cbd |
completed | April 29, 2026, 6:36 a.m. |
Created at: April 17, 2026, 5:55 p.m.