Triple

T6532494
Position Surface form Disambiguated ID Type / Status
Subject Albium Ingaunum E152264 entity
Predicate knownAs P39 FINISHED
Object Albingaunum Ingaunum E605608 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: Albingaunum Ingaunum | Statement: [Albium Ingaunum, knownAs, Albingaunum Ingaunum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Albingaunum Ingaunum
Context triple: [Albium Ingaunum, knownAs, Albingaunum Ingaunum]
  • A. Albingaunum chosen
    Albingaunum is the ancient Roman name for the Ligurian coastal town now known as Albenga in northwestern Italy.
  • B. Gesoriacum
    Gesoriacum was the ancient Roman name for the port city later known as Bononia (modern Boulogne-sur-Mer) in northern Gaul, an important maritime and military hub facing Britain.
  • C. Andecavorum
    Andecavorum is the ancient Latin name for the city now known as Angers in western France.
  • D. Maenza
    Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
  • E. Misenum
    Misenum was an important ancient Roman naval base and coastal town located at the northwestern end of the Bay of Naples in Italy.
  • 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_69c688048ec8819093a47f7d332e12ec completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6adbe168881908ffefc4962e2893d completed March 27, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6e41908f0819096e6e432509afe7d completed March 27, 2026, 8:10 p.m.
Created at: March 27, 2026, 1:46 p.m.