Triple

T1761814
Position Surface form Disambiguated ID Type / Status
Subject Latium E38673 entity
Predicate contains P35 FINISHED
Object Ostia E83891 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: Ostia | Statement: [Latium, contains, Ostia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ostia
Context triple: [Latium, contains, Ostia]
  • A. Ostia chosen
    Ostia was the principal harbor city of ancient Rome, serving as a major commercial and military port at the mouth of the Tiber River.
  • B. Civitavecchia
    Civitavecchia is a major Italian port city in the Lazio region that serves as the principal maritime gateway to Rome on the Tyrrhenian coast.
  • C. Alba Longa
    Alba Longa was an ancient Latin city in central Italy, traditionally regarded as the mother city of Rome and the seat of the Alban kings.
  • D. Velletri
    Velletri is a historic town in the Lazio region of central Italy, known for its ancient Roman roots, wine production, and location in the Alban Hills southeast of Rome.
  • E. Pomezia
    Pomezia is a modern industrial and residential town in the Lazio region of central Italy, situated just south of Rome.
  • 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_69a8862d562481908d7025a1c1f67c0d completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa6463ac0081909e9ebe6ebf1db857 completed March 6, 2026, 5:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69adf3bc8fe8819085a8adaf9dcd5c1b completed March 8, 2026, 10:10 p.m.
Created at: March 4, 2026, 7:31 p.m.