Triple

T15216459
Position Surface form Disambiguated ID Type / Status
Subject Bybanen E363648 entity
Predicate owner P347 FINISHED
Object Skyss E629363 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: Skyss | Statement: [Bybanen, owner, Skyss]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skyss
Context triple: [Bybanen, owner, Skyss]
  • A. Skyss chosen
    Skyss is the public transport authority for Vestland county in Norway, responsible for coordinating bus, light rail, and some ferry services in the Bergen region.
  • B. Karakays
    Karakays are an ethnic community historically associated with the region of Gözleve (modern-day Yevpatoria) in Crimea.
  • C. Byxelkrok
    Byxelkrok is a small coastal village and popular summer destination on the northern part of the Swedish island of Öland.
  • D. Rycken
    Rycken is a Dutch-origin surname historically borne by families such as that of Abraham Rycken in the Low Countries and early colonial America.
  • E. Syvota
    Syvota is a coastal village and popular tourist resort on the Ionian Sea in northwestern Greece, known for its scenic bays and nearby islands.
  • 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0076f90c481909989befe031a2cae completed April 15, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fed343f51481908f04c35d37b39ad2 completed May 9, 2026, 6:25 a.m.
Created at: April 10, 2026, 3:11 a.m.