Triple

T3947992
Position Surface form Disambiguated ID Type / Status
Subject UCI ProTeams (by invitation) E84792 entity
Predicate selectionCriteriaMayInclude P36515 FINISHED
Object sporting performance 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: sporting performance | Statement: [UCI ProTeams (by invitation), selectionCriteriaMayInclude, sporting performance]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: selectionCriteriaMayInclude
Context triple: [UCI ProTeams (by invitation), selectionCriteriaMayInclude, sporting performance]
  • A. selectionCriteria
    Indicates the conditions or rules used to choose certain entities from a larger set.
  • B. evaluationCriteriaInclude chosen
    Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
  • C. listingCriterion
    Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
  • D. selectionCharacteristic
    Indicates a distinguishing feature or criterion used to choose or differentiate one entity from others.
  • E. includesClause
    Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
  • 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_69aed934fbfc8190847068e4546de963 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefaa5afdc8190b709af2473d75d02 completed March 9, 2026, 4:51 p.m.
PD Predicate disambiguation batch_69aef8ed04e4819096bced8971cd888d completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:30 p.m.