Triple

T36495656
Position Surface form Disambiguated ID Type / Status
Subject Rende E899178 entity
Predicate hasModernDistrict P58091 FINISHED
Object Quattromiglia 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: Quattromiglia | Statement: [Rende, hasModernDistrict, Quattromiglia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasModernDistrict
Context triple: [Rende, hasModernDistrict, Quattromiglia]
  • A. hasModernAdministrativeUnit
    Indicates that an entity is associated with or belongs to a current, officially recognized administrative unit (such as a modern country, state, province, or municipality).
  • B. containsModernCity chosen
    Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
  • C. hasModernTerritory
    Indicates that an entity (typically a historical or former polity) corresponds geographically to the present-day territory of another entity (usually a modern state or region).
  • D. hasModernNearbyCity
    Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
  • E. modernDistrict
    Indicates that one administrative district is the contemporary or current counterpart of another, typically older or historical, district.
  • 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_69f76e5ad4588190bdbce60c52fbb785 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69ff63225b6481909217ad11b4f7d3ba completed May 9, 2026, 4:38 p.m.
PD Predicate disambiguation batch_69ff60e0882c819085d097010db43ee0 completed May 9, 2026, 4:29 p.m.
Created at: May 3, 2026, 4:10 p.m.