Triple

T27017258
Position Surface form Disambiguated ID Type / Status
Subject Verbanesi E680567 entity
Predicate associatedWithFormerTowns P194301 FINISHED
Object Intra 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: Intra | Statement: [Verbanesi, associatedWithFormerTowns, Intra]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithFormerTowns
Context triple: [Verbanesi, associatedWithFormerTowns, Intra]
  • A. associatedWithFormerCity
    Indicates a relationship where an entity is or was connected to a city that no longer exists in its former status or form (e.g., renamed, dissolved, or merged).
  • B. hasAssociatedCityFormerName
    Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
  • C. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • D. associatedWithCityHistory
    Indicates a relationship where something is connected or relevant to the historical events, development, or heritage of a particular city.
  • E. containsFormerMunicipality chosen
    Indicates that an administrative unit includes within its boundaries an area that was previously an independent municipality.
  • 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_69eeeb5450988190bfc9a3c012ac463a completed April 27, 2026, 4:51 a.m.
NER Named-entity recognition batch_69ff9bed58dc8190a204816d4ed6c32c completed May 9, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69ff9b69653c81908ab0d88055a66a88 completed May 9, 2026, 8:39 p.m.
Created at: April 27, 2026, 7:06 a.m.