Triple
T11199953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Asculum |
E265012
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Asculum |
E352707
|
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: Asculum | Statement: [Battle of Asculum, location, Asculum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Asculum Context triple: [Battle of Asculum, location, Asculum]
-
A.
Asculum
chosen
Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
-
B.
Arpinum
Arpinum is an ancient Italian town in Latium best known as the birthplace of the Roman statesman and orator Cicero.
-
C.
Falciano
Falciano is a village and civil parish in the Republic of San Marino, forming part of the municipality of Serravalle.
-
D.
Laurentum
Laurentum was an ancient coastal city in Latium, traditionally associated with the legendary king Latinus and early Roman mythic history.
-
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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8c1e9f88190b2b42326aba9d778 |
completed | April 9, 2026, 5:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4970df7cc81909c3b07ead58513e8 |
completed | April 19, 2026, 8:49 a.m. |
Created at: April 8, 2026, 9:29 p.m.