Triple

T34987601
Position Surface form Disambiguated ID Type / Status
Subject Brian Kilrea E1008993 entity
Predicate competitiveLevelAsPlayer P180985 FINISHED
Object professional 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: professional | Statement: [Brian Kilrea, competitiveLevelAsPlayer, professional]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: competitiveLevelAsPlayer
Context triple: [Brian Kilrea, competitiveLevelAsPlayer, professional]
  • A. competitionLevelOf
    Indicates the degree or intensity of competitiveness associated with an entity, event, or context.
  • B. competitionLevel
    Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
  • C. competesAtLevel chosen
    Indicates that one entity participates in competition at a specified level or tier relative to others.
  • D. competitionLevelRelativeToAmateur
    Indicates the degree to which something’s level of competition differs from that of an amateur level.
  • E. teamLevel
    Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
  • 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_69f76dc844a48190881951fffb83d17e completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fcab6e888881908ca9e18660928a40 completed May 7, 2026, 3:10 p.m.
PD Predicate disambiguation batch_69fc4562a5b88190bad48f083a6dcdfa completed May 7, 2026, 7:55 a.m.
Created at: May 3, 2026, 4:01 p.m.