Triple
T8310099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arpinum |
E194569
|
entity |
| Predicate | hasLatinName |
P3646
|
FINISHED |
| Object | Arpinum |
E194569
|
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: Arpinum | Statement: [Arpinum, hasLatinName, Arpinum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Arpinum Context triple: [Arpinum, hasLatinName, Arpinum]
-
A.
Arpinum
chosen
Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
-
B.
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.
-
C.
Asculum
Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
-
D.
Ferentinum
Ferentinum was an ancient town in central Italy historically associated with the Hernici people and later integrated into the Roman sphere.
-
E.
Alatri
Alatri is a historic hill town in Italy’s Lazio region, renowned for its well-preserved ancient polygonal walls and acropolis dating back to the pre-Roman era.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f2d2c30819095075940479b75a7 |
completed | March 31, 2026, 8 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde77d43cc8190ad18e932d9230e5c |
completed | April 2, 2026, 3:50 a.m. |
Created at: March 30, 2026, 5:54 p.m.