Triple
T16451876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio IV Samnium |
E399571
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Saepinum |
E222907
|
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: Saepinum | Statement: [Regio IV Samnium, contains, Saepinum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saepinum Context triple: [Regio IV Samnium, contains, Saepinum]
-
A.
Saepinum
chosen
Saepinum was an ancient town of the Samnite people in south-central Italy, later developed into a Roman municipium whose ruins are still visible today.
-
B.
Sabinum
Sabinum was the ancient central Italian region traditionally associated with the Sabine people, located in the Apennine area northeast of Rome.
-
C.
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.
-
D.
Asculum
Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
-
E.
Glanum
Glanum is an ancient Greco-Roman city in southern France known for its well-preserved ruins and monumental architecture.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ce19344819083d323077b742bc3 |
completed | April 18, 2026, 7:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0045979c588190b6f7b249147f3174 |
completed | May 10, 2026, 8:45 a.m. |
Created at: April 10, 2026, 5:10 a.m.