Triple

T19486022
Position Surface form Disambiguated ID Type / Status
Subject Kristīne Opolais E487513 entity
Predicate familyName P18 FINISHED
Object Opolais 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: Opolais | Statement: [Kristīne Opolais, familyName, Opolais]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opolais
Context triple: [Kristīne Opolais, familyName, Opolais]
  • A. Opolais chosen
    Opolais is the surname of Latvian soprano opera singer Kristīne Opolais, renowned for her dramatic roles on major international stages.
  • B. Opol
    Opol is a coastal municipality in Misamis Oriental, Philippines, known for its beaches, eco-tourism attractions, and proximity to Cagayan de Oro City.
  • C. Opoeteren
    Opoeteren is a village in the Belgian province of Limburg that now forms part of the municipality of Maaseik.
  • D. Opañel
    Opañel is a Madrid Metro station serving the Carabanchel district in Spain.
  • E. Opoji
    Opoji is a town and traditional community within the Esan ethnic area of Edo State, Nigeria, known for its indigenous customs and local governance structures.
  • 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_69d8e8d924388190b847cb15bb3d0aff completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6343f46e88190b7ba65c210285bee completed April 20, 2026, 2:12 p.m.
Created at: April 10, 2026, 1:39 p.m.