Triple

T2993413
Position Surface form Disambiguated ID Type / Status
Subject LSK Kvinner FK E81008 entity
Predicate regularlyCompetesFor P39898 FINISHED
Object Toppserien title LITERAL 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: Toppserien title | Statement: [LSK Kvinner FK, regularlyCompetesFor, Toppserien title]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regularlyCompetesFor
Context triple: [LSK Kvinner FK, regularlyCompetesFor, Toppserien title]
  • A. competeIn chosen
    Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
  • B. competedFor
    Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
  • C. hasCompetition
    Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
  • D. competitionOf
    Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
  • E. competesWith
    Indicates that two entities are in rivalry or opposition, each striving to outperform or gain advantage over the other in the same domain or objective.
  • F. None of above.

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_69ad8b187fc8819085914d3c9ea3142d completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad99e12c5c8190af7cc20e4c48bf45 completed March 8, 2026, 3:46 p.m.
PD Predicate disambiguation batch_69ad961403108190bbecb8d3608fd4e0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:59 p.m.