Triple

T14006864
Position Surface form Disambiguated ID Type / Status
Subject Via Severiana E336970 entity
Predicate servedSettlement P2741 FINISHED
Object Laurentum E468400 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: Laurentum | Statement: [Via Severiana, servedSettlement, Laurentum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Laurentum
Context triple: [Via Severiana, servedSettlement, Laurentum]
  • A. Laurentum chosen
    Laurentum was an ancient coastal city in Latium, traditionally associated with the legendary king Latinus and early Roman mythic history.
  • B. Asculum
    Asculum was an important ancient city in central Italy, historically serving as the chief urban center of the Piceni people.
  • C. Maenza
    Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
  • D. Lauriacum
    Lauriacum was a major Roman military and administrative center in the province of Noricum, located near the Danube in what is now Austria.
  • E. Argiletum
    Argiletum was an ancient street in Rome that connected the Roman Forum to the Subura district and later became partly occupied by the Forum of Nerva.
  • 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_69d81c645c5c8190b1fd16a285a1b78a completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2ed327d88190a53af5768468a8eb completed April 14, 2026, 12:10 p.m.
NED1 Entity disambiguation (via context triple) batch_69fbc329891c8190b4dcb9913e235a1c completed May 6, 2026, 10:39 p.m.
Created at: April 9, 2026, 10:19 p.m.