Triple

T17481665
Position Surface form Disambiguated ID Type / Status
Subject Golasecca III E425673 entity
Predicate hasTypeSite P44791 FINISHED
Object Golasecca 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: Golasecca | Statement: [Golasecca III, hasTypeSite, Golasecca]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Golasecca
Context triple: [Golasecca III, hasTypeSite, Golasecca]
  • A. Golasecca chosen
    Golasecca is a town in northern Italy known for giving its name to the Iron Age Golasecca culture discovered in the surrounding area.
  • B. Gallarate
    Gallarate is a town in the Lombardy region of northern Italy, situated in the province of Varese and forming part of the greater Milan metropolitan area.
  • C. Zagarolo
    Zagarolo is a historic hill town in the Lazio region of central Italy, known for its medieval center and proximity to Rome.
  • D. Quarracino
    Quarracino is an Italian-origin surname most notably associated with Argentine Cardinal Antonio Quarracino.
  • E. Grosio
    Grosio is a municipality in the Valtellina valley of Lombardy, northern Italy, known for its Alpine setting and proximity to major mountain passes.
  • 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_69d889dccf7481909264a1844a2e9100 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e451bfd75481908c20bc2c1cbff593 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 5:48 a.m.