Triple

T15889940
Position Surface form Disambiguated ID Type / Status
Subject Solkan Bridge E385290 entity
Predicate locatedIn P40 FINISHED
Object Solkan E383476 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: Solkan | Statement: [Solkan Bridge, locatedIn, Solkan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Solkan
Context triple: [Solkan Bridge, locatedIn, Solkan]
  • A. Solkan chosen
    Solkan is a settlement in western Slovenia, known for its historic stone railway bridge over the Soča River and its proximity to the town of Nova Gorica.
  • B. Slanica
    Slanica was a former Slovak village in the Orava region that was submerged during the creation of the Orava Reservoir, with only its church preserved on an island as a memorial.
  • C. Plesac
    Plesac is a surname most notably associated with former Major League Baseball pitcher and current broadcaster Dan Plesac.
  • D. Zachenberg
    Zachenberg is a small municipality in the Bavarian Forest region of southeastern Germany.
  • E. Suchdol
    Suchdol is a residential and university district on the northwestern edge of Prague, known for hosting the Czech University of Life Sciences and offering a semi-rural atmosphere overlooking the Vltava valley.
  • 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_69d86da5b800819083a31be937d738b0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1561d5c28819094c3541d917a4433 completed April 16, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffb047b6248190b6c11ef20636f50f completed May 9, 2026, 10:08 p.m.
Created at: April 10, 2026, 4:51 a.m.