Triple

T22173421
Position Surface form Disambiguated ID Type / Status
Subject Ornö village E547980 entity
Predicate locatedIn P40 FINISHED
Object Ornö 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: Ornö | Statement: [Ornö village, locatedIn, Ornö]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ornö
Context triple: [Ornö village, locatedIn, Ornö]
  • A. Ornö chosen
    Ornö is a large island in the Stockholm archipelago of Sweden, known for its forests, bays, and traditional summer cottages.
  • B. Ngäsinue Island
    Ngäsinue Island is a small island in the Solomon Islands’ Temotu Province, notable as one of the primary communities of Äiwoo language speakers.
  • C. Slovanský Island
    Slovanský Island is a small historic island in central Prague known for its cultural venues, scenic riverside views, and recreational spaces along the Vltava River.
  • D. Granvin
    Granvin is a small village and former municipality in Vestland county, Norway, known for its scenic fjord landscape and traditional rural character within the Hardanger region.
  • E. Øyeren
    Øyeren is a large lake in southeastern Norway, known for its rich birdlife and role as a major reservoir along the Glomma river system.
  • 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_69e11e3d53f88190a2b690e3f25bb062 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f12a6a9370819098ad65fede676c2b completed April 28, 2026, 9:45 p.m.
Created at: April 16, 2026, 8:34 p.m.