Triple

T6661066
Position Surface form Disambiguated ID Type / Status
Subject Sorbo necropolis E151475 entity
Predicate locatedIn P40 FINISHED
Object Caere E151475 NE 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: Caere | Statement: [Sorbo necropolis, locatedIn, Caere]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Caere
Context triple: [Sorbo necropolis, locatedIn, Caere]
  • A. Caere chosen
    Caere was a major ancient Etruscan city-state in central Italy, noted for its wealth, maritime trade, and close cultural contacts with the Greek and Phoenician worlds.
  • B. Caer
    Caer is an old Welsh-derived name historically used for the city now known as Chester in northwest England.
  • C. Carentan
    Carentan is a small town in Normandy, France, known for its strategic role in the D-Day landings and subsequent World War II battles.
  • D. Tarsos
    Tarsos is the ancient name of the historic city of Tarsus in Cilicia, a significant cultural and commercial center in the eastern Mediterranean world.
  • E. Carnan
    Carnan is a small settlement on South Uist in Scotland’s Outer Hebrides.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c687f5fac48190a09e4838d9c6b45d completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6b0737cb08190ad455b48fd30eec8 completed March 27, 2026, 4:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c700755874819083cd0facebd7aa3d completed March 27, 2026, 10:11 p.m.
Created at: March 27, 2026, 2:02 p.m.