Triple

T10644974
Position Surface form Disambiguated ID Type / Status
Subject Osona E250812 entity
Predicate contains P35 FINISHED
Object Sora E339644 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: Sora | Statement: [Osona, contains, Sora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sora
Context triple: [Osona, contains, Sora]
  • A. Sora chosen
    Sora is a historic town and comune in the Lazio region of central Italy, situated along the Liri River and known for its medieval architecture and scenic surroundings.
  • B. Duke of Sora
    The Duke of Sora was a noble title in the Kingdom of Naples historically associated with the influential Italian della Rovere family.
  • C. Roxas
    Roxas is a Filipino surname most prominently associated with Manuel Roxas, the fifth President of the Philippines and the first leader of the independent Third Republic.
  • D. Roxas
    Roxas is a coastal municipality in the Philippine province of Palawan known for its fishing industry and access to nearby island and marine attractions.
  • E. Ness
    Ness is a remote crofting and fishing community at the northern tip of the Isle of Lewis 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_69d6aa5a4c4881908f39be6efe5981e5 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dfe120908190ab91c38d57133739 completed April 8, 2026, 11:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69d97a580d388190aea5edadd4afc0d1 completed April 10, 2026, 10:31 p.m.
Created at: April 8, 2026, 9:05 p.m.