Triple

T24890620
Position Surface form Disambiguated ID Type / Status
Subject FIRST Tech Challenge judged awards set E622987 entity
Predicate excludesAwardType P56586 FINISHED
Object match play awards 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: match play awards | Statement: [FIRST Tech Challenge judged awards set, excludesAwardType, match play awards]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: excludesAwardType
Context triple: [FIRST Tech Challenge judged awards set, excludesAwardType, match play awards]
  • A. excludesAward chosen
    Indicates that one entity explicitly omits or disqualifies another entity from receiving a particular award.
  • B. appliesToAwardType
    Indicates that a rule, condition, or attribute is specifically relevant or applicable to a particular type or category of award.
  • C. cannotBeAwardedTo
    Indicates that a particular entity is ineligible to receive a specified award, prize, or recognition.
  • D. notAwardedIn
    Indicates that a particular award or recognition was not given to an entity within a specified context, such as a year, event, or category.
  • E. excludedFrom
    Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
  • 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_69e2fac597708190a922bf39a49ec70a completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f464b4c9b0819085daa00c7c3b8b76 completed May 1, 2026, 8:30 a.m.
PD Predicate disambiguation batch_69f45cf017a88190b4985b11159c907d completed May 1, 2026, 7:57 a.m.
Created at: April 18, 2026, 5:26 a.m.