Triple

T20018193
Position Surface form Disambiguated ID Type / Status
Subject Skodje stone arch bridge E494777 entity
Predicate locatedIn P40 FINISHED
Object Skodje 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: Skodje | Statement: [Skodje stone arch bridge, locatedIn, Skodje]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skodje
Context triple: [Skodje stone arch bridge, locatedIn, Skodje]
  • A. Skodje chosen
    Skodje is a village and former municipality in western Norway, known for its scenic fjord landscape and historic stone arch bridge.
  • B. Skrad
    Skrad is a small mountain town in Croatia’s Gorski Kotar region, known for its forested landscapes, hiking trails, and nearby natural attractions such as canyons and waterfalls.
  • C. Skorba
    Skorba is an archaeological temple site in Malta, notable for its prehistoric megalithic structures that form part of the island’s ancient temple complex heritage.
  • D. Skopin
    Skopin is a historic town in western Russia known for its traditional pottery and ceramics industry.
  • E. Kopaska
    Kopaska is the Indonesian Navy’s elite frogman and special operations unit, specializing in underwater demolition, maritime sabotage, and counter-terrorism missions.
  • 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_69da626bfd288190aa5d65098b6433ae completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e6623d76808190988990a8dc263ef7 completed April 20, 2026, 5:28 p.m.
Created at: April 11, 2026, 3:34 p.m.