Triple

T16736378
Position Surface form Disambiguated ID Type / Status
Subject Olesko Castle E406728 entity
Predicate locatedIn P40 FINISHED
Object Olesko E406728 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: Olesko | Statement: [Olesko Castle, locatedIn, Olesko]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Olesko
Context triple: [Olesko Castle, locatedIn, Olesko]
  • A. Olesko chosen
    Olesko is a historic town in western Ukraine best known for its medieval castle, which served as the birthplace of Polish King John III Sobieski.
  • B. Ossoli
    Ossoli is an Italian surname historically associated with figures such as Angelo Eugene Ossoli and the noble Ossoli family.
  • C. Oxenberg
    Oxenberg is a surname most prominently associated with actress Catherine Oxenberg, known for her role on the television series "Dynasty" and her ties to European royalty.
  • D. Owaneco
    Owaneco was a prominent Mohegan sachem (chief) known for his leadership and land dealings in colonial New England during the late 17th and early 18th centuries.
  • E. Koules
    Koules is a Venetian-era coastal fortress in Heraklion, Crete, that historically protected the city’s harbor and now serves as a prominent cultural and tourist landmark.
  • 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_69d8838ffb088190a0b11149929006bf completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e39c3a86848190a03f243dd1bdb899 completed April 18, 2026, 2:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a009d4ea8208190aed0a4014a10d120 completed May 10, 2026, 2:59 p.m.
Created at: April 10, 2026, 5:20 a.m.