Triple

T18154775
Position Surface form Disambiguated ID Type / Status
Subject Campo Imperatore E434600 entity
Predicate hasRoadAccessFrom P22549 FINISHED
Object Assergi 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: Assergi | Statement: [Campo Imperatore, hasRoadAccessFrom, Assergi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Assergi
Context triple: [Campo Imperatore, hasRoadAccessFrom, Assergi]
  • A. Assergi chosen
    Assergi is a small village in Italy’s Abruzzo region, situated on the slopes of Gran Sasso and known as a gateway to the surrounding national park and mountain research facilities.
  • B. Asserbos
    Asserbos is a historic urban forest and public park located in the city of Assen in the Netherlands.
  • C. Asomante
    Asomante is a rural barrio (district) of the municipality of Aibonito in Puerto Rico, known for its mountainous landscape and cool climate.
  • D. Assino
    Assino is a minor river in central Italy that flows through Umbria before joining the Chiascio River.
  • E. Mandonio
    Mandonio was an Iberian chieftain who led resistance against Roman expansion during the conquest of the Iberian Peninsula.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4de3b5b788190b011c4eb96a71ffd completed April 19, 2026, 1:52 p.m.
Created at: April 10, 2026, 10:30 a.m.