Triple
T1906863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Aemilia |
E38023
|
entity |
| Predicate | startPoint |
P389
|
FINISHED |
| Object | Ariminum |
E212525
|
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: Ariminum | Statement: [Via Aemilia, startPoint, Ariminum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ariminum Context triple: [Via Aemilia, startPoint, Ariminum]
-
A.
Ariminum
chosen
Ariminum was an important ancient Roman city on the Adriatic coast of Italy, known today as Rimini.
-
B.
Argentoratum
Argentoratum is the ancient Roman military camp and settlement that later developed into the modern city of Strasbourg in northeastern France.
-
C.
Arpinum
Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
-
D.
Beneventum
Beneventum was an important ancient Roman city in southern Italy, strategically located as a key junction on major roads and known for its military and commercial significance.
-
E.
Clusium
Clusium was an important ancient Etruscan city, known for its strategic location in central Italy and its significant role in early Roman history.
- 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_69a8862a26088190aae5243695aeefc0 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1b3217081909004ad7f687b4216 |
completed | March 7, 2026, 5:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adfbac4e18819081f6cfdf1cd7a03c |
completed | March 8, 2026, 10:43 p.m. |
Created at: March 4, 2026, 7:35 p.m.