Triple

T23148413
Position Surface form Disambiguated ID Type / Status
Subject Diocese of Andria E578256 entity
Predicate locatedIn P40 FINISHED
Object Andria 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: Andria | Statement: [Diocese of Andria, locatedIn, Andria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Andria
Context triple: [Diocese of Andria, locatedIn, Andria]
  • A. Andria chosen
    Andria is a historic city in the Apulia region of southern Italy, known for its proximity to the UNESCO-listed Castel del Monte and its rich medieval heritage.
  • B. Andrada
    Andrada is a Portuguese-language surname most notably associated with Brazilian statesman and independence leader José Bonifácio de Andrada e Silva.
  • C. Doirani
    Doirani is a settlement in northern Greece near Lake Doirani, close to the border with North Macedonia, known for its historical significance in the Balkan Wars and World War I.
  • D. Daulida
    Daulida is an alternative name for the ancient Greek town of Daulis in the region of Phocis.
  • E. Laranda
    Laranda was an important ancient city in the region of Lycaonia in central Anatolia, known from Hellenistic and Roman times.
  • 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ecf9e9881908991ede784158f1e completed April 29, 2026, 4:53 a.m.
Created at: April 17, 2026, 4:01 p.m.