Triple
T2303968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhegion |
E51793
|
entity |
| Predicate | laterName |
P65
|
FINISHED |
| Object | Rhegium Julium |
E52279
|
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: Rhegium Julium | Statement: [Rhegion, laterName, Rhegium Julium]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rhegium Julium Context triple: [Rhegion, laterName, Rhegium Julium]
-
A.
Praeneste
Praeneste was an ancient Italian city in Latium, famed for its monumental sanctuary of Fortuna Primigenia and its strategic position overlooking the Roman Campagna.
-
B.
Rhegium
chosen
Rhegium was an important ancient Greek colony in southern Italy, located at the Strait of Messina and known for its strategic and commercial significance in Magna Graecia.
-
C.
Arpinum
Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
-
D.
Aquincum
Aquincum was an important ancient Roman military and civilian settlement located in what is now northern Budapest, Hungary.
-
E.
Brundisium
Brundisium was an important ancient Roman port city in southern Italy, strategically located on the Adriatic Sea and serving as a major gateway to the eastern 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc5f2de7c819095bd74a551d8ff18 |
completed | March 7, 2026, 6:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae89575e648190a2e7b5b2e011bd30 |
completed | March 9, 2026, 8:48 a.m. |
Created at: March 4, 2026, 7:49 p.m.