Triple
T14269408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Gallicus |
E353738
|
entity |
| Predicate | majorCity |
P316
|
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: [Ager Gallicus, majorCity, Ariminum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ariminum Context triple: [Ager Gallicus, majorCity, 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.
Argiletum
Argiletum was an ancient street in Rome that connected the Roman Forum to the Subura district and later became partly occupied by the Forum of Nerva.
-
E.
Asculum
Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de657fe6708190b41de48c43cff647 |
completed | April 14, 2026, 4:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd32682a0481908918570a778e185a |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 10, 2026, 1:10 a.m.