Triple

T35415861
Position Surface form Disambiguated ID Type / Status
Subject Comune di Collegno E1023638 entity
Predicate hasTerritorialCodeType P32496 FINISHED
Object Italian ISTAT municipal code LITERAL 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: Italian ISTAT municipal code | Statement: [Comune di Collegno, hasTerritorialCodeType, Italian ISTAT municipal code]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTerritorialCodeType
Context triple: [Comune di Collegno, hasTerritorialCodeType, Italian ISTAT municipal code]
  • A. territoryCode chosen
    Indicates the standardized code assigned to a specific geographic or administrative territory in the relationship.
  • B. hasTerritorialSubdivisionType
    Indicates that an entity’s territorial subdivisions are of a specified administrative or geographic type (e.g., province, county, district).
  • C. hasProvincialCode
    Indicates that an entity is associated with a specific provincial code that identifies its province or administrative region.
  • D. hasDefinedTerritory
    Indicates that an entity possesses a specific, delimited geographic or conceptual area over which it has recognized control or jurisdiction.
  • E. hasCanonicalTerritory
    Indicates that an entity possesses an officially recognized or standard territorial area associated with it.
  • F. None of above.

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_69f76df54bac8190bd0d3b0eb35cda5f completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69fe6fea4a288190bf8615c5d6bf41b4 completed May 8, 2026, 11:21 p.m.
PD Predicate disambiguation batch_69fe6f774de08190975a2393b9a1fd22 completed May 8, 2026, 11:19 p.m.
Created at: May 3, 2026, 4:03 p.m.