Triple
T16391096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Anglorum |
E398051
|
entity |
| Predicate | precedes |
P97
|
FINISHED |
| Object | Rex Angliae |
E398051
|
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 Angliae | Statement: [Rex Anglorum, precedes, Rex Angliae]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rex Angliae Context triple: [Rex Anglorum, precedes, Rex Angliae]
-
A.
Rex Anglorum
chosen
Rex Anglorum is a Latin royal title historically used to denote the "King of the English" in medieval England.
-
B.
Rex Britanniae
Rex Britanniae is a Latin royal style meaning "King of Britain," used to assert overlordship or supremacy over the whole island beyond a ruler’s own kingdom.
-
C.
Rex Hiberniae
Rex Hiberniae was the Latin royal title meaning "King of Ireland," historically used to denote the monarch claiming sovereignty over the whole island.
-
D.
Rex Hungariae
Rex Hungariae is the Latin royal title historically used for the kings of Hungary, including Stephen V.
-
E.
Bigod
Bigod is an Anglo-Norman noble family prominent in medieval England, particularly known for holding the earldom of Norfolk and playing key roles in royal politics.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326425c8081908cacffcfa8c7386b |
completed | April 18, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a003c58280081908e4d73a75b09dbb8 |
completed | May 10, 2026, 8:05 a.m. |
Created at: April 10, 2026, 5:08 a.m.