Triple
T8388473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cisalpine Gaul |
E197879
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Mutina |
E212294
|
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: Mutina | Statement: [Cisalpine Gaul, capital, Mutina]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mutina Context triple: [Cisalpine Gaul, capital, Mutina]
-
A.
Mutina
chosen
Mutina was an important ancient Roman city in northern Italy, known today as Modena.
-
B.
Maiolus
Maiolus was a 10th-century Benedictine monk and influential abbot of Cluny, known for his role in monastic reform across medieval Europe.
-
C.
Sabinum
Sabinum was the ancient central Italian region traditionally associated with the Sabine people, located in the Apennine area northeast of Rome.
-
D.
Canova
Canova was a renowned Italian Neoclassical sculptor celebrated for his marble masterpieces depicting mythological and historical subjects.
-
E.
Maenza
Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81090f688190a3a8d1680383c361 |
completed | March 31, 2026, 8:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde83aac448190b74f65507170a8f7 |
completed | April 2, 2026, 3:53 a.m. |
Created at: March 30, 2026, 6:03 p.m.