Triple
T19438239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osimo |
E486279
|
entity |
| Predicate | hasAncientName |
P20952
|
FINISHED |
| Object | Auximum |
—
|
NE NERFINISHED |
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: Auximum | Statement: [Osimo, hasAncientName, Auximum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Auximum Context triple: [Osimo, hasAncientName, Auximum]
-
A.
Auximum
chosen
Auximum, known today as Osimo, is an ancient hilltop town in Italy’s Marche region that served as an important settlement of the Picentes and later a Roman municipium.
-
B.
Ampsin
Ampsin is a village in the province of Liège, Belgium, known as a district of the municipality of Amay along the Meuse River.
-
C.
Axamo
Axamo is a locality in Jönköping Municipality in southern Sweden, known primarily for its proximity to Jönköping Airport.
-
D.
Auxini
Auxini was a Spanish construction and engineering company that later became part of the ACS Group through a merger.
-
E.
Altiora Petimus
Altiora Petimus is a Latin motto meaning "We seek higher things," expressing an aspiration toward greater achievement and excellence.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6336281b88190b1e5ad2606d7c314 |
completed | April 20, 2026, 2:08 p.m. |
Created at: April 10, 2026, 1:38 p.m.