Triple
T9523541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rex Siciliae |
E229701
|
entity |
| Predicate | usedAlongside |
P4791
|
FINISHED |
| Object | Rex Hierosolymae |
E44866
|
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 Hierosolymae | Statement: [Rex Siciliae, usedAlongside, Rex Hierosolymae]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rex Hierosolymae Context triple: [Rex Siciliae, usedAlongside, Rex Hierosolymae]
-
A.
Rex Neapolis
Rex Neapolis is a historical royal title associated with the kingship of Naples in the Italian peninsula.
-
B.
Rex Merciorum
Rex Merciorum is the Latin royal title meaning "King of the Mercians," historically associated with rulers of the Anglo-Saxon kingdom of Mercia such as Offa.
-
C.
Rex Iudaeorum
Rex Iudaeorum is the Latin phrase meaning "King of the Jews," famously associated with the inscription placed on the cross of Jesus in Christian tradition.
-
D.
Rex Scottorum
Rex Scottorum is the Latin royal title meaning "King of the Scots," historically used by Scottish monarchs such as Alexander I.
-
E.
Jebus
chosen
Jebus is the ancient Canaanite name for the city later known as Jerusalem.
- 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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9898e0b48190a3e3f0f1616d5055 |
completed | April 1, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d13a61fbd08190bb68ffe29da3a34a |
completed | April 4, 2026, 4:20 p.m. |
Created at: March 30, 2026, 7:59 p.m.