Triple

T13781869
Position Surface form Disambiguated ID Type / Status
Subject Scottish Open E331149 entity
Predicate hasRankingStatus P110944 FINISHED
Object ranking event 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: ranking event | Statement: [Scottish Open, hasRankingStatus, ranking event]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRankingStatus
Context triple: [Scottish Open, hasRankingStatus, ranking event]
  • A. hasRankingCategory
    Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
  • B. rankingStatus chosen
    Indicates the relative position or level an entity holds within an ordered ranking or hierarchy.
  • C. hasRankingUnit
    Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
  • D. hasRankingFactor
    Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
  • E. isRanked
    Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
  • 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_69d81c583b0081909e408a17db517a21 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de0247ccc881908dad7b547221f15d completed April 14, 2026, 9 a.m.
PD Predicate disambiguation batch_69dbc85fb600819098a2aab48169be96 completed April 12, 2026, 4:29 p.m.
Created at: April 9, 2026, 10:11 p.m.