Triple

T10018612
Position Surface form Disambiguated ID Type / Status
Subject Lanuvium E199557 entity
Predicate hasAlternativeName P39 FINISHED
Object Lanuvio E199557 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: Lanuvio | Statement: [Lanuvium, hasAlternativeName, Lanuvio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lanuvio
Context triple: [Lanuvium, hasAlternativeName, Lanuvio]
  • A. Lanuvium chosen
    Lanuvium was an ancient Latin city in central Italy, noted for its important sanctuary of Juno Sospita and its later incorporation into the Roman state.
  • B. Vezio
    Vezio is a small village in northern Italy overlooking Lake Como, known for its scenic views and the medieval Castello di Vezio.
  • C. Bucchianico
    Bucchianico is a small Italian town in the Abruzzo region, known for its historic hilltop setting and traditional festivals.
  • D. Larciano
    Larciano is a small Italian municipality in Tuscany known for its medieval castle and scenic location in the Valdinievole area.
  • E. Falciano
    Falciano is a village and civil parish in the Republic of San Marino, forming part of the municipality of Serravalle.
  • 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_69ca8315a1a08190ab310f25620f362b completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd4de1588190a89ed575cff0b8c9 completed April 2, 2026, 1:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2b60256b48190829cfdbff0105cc0 completed April 5, 2026, 7:20 p.m.
Created at: March 30, 2026, 8:53 p.m.