Triple

T31673578
Position Surface form Disambiguated ID Type / Status
Subject AUS E808336 entity
Predicate isCommonlyUsedInSportsContexts P5086 FINISHED
Object true 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: true | Statement: [AUS, isCommonlyUsedInSportsContexts, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCommonlyUsedInSportsContexts
Context triple: [AUS, isCommonlyUsedInSportsContexts, true]
  • A. usedInSport chosen
    Indicates that something (such as an object, technique, or concept) is employed or utilized within the context of a particular sport.
  • B. alsoUsedForSport
    Indicates that something primarily associated with one purpose is additionally used for sporting activities or athletic purposes.
  • C. hasSportingContext
    Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
  • D. usedSportFor
    Indicates that an entity employs or utilizes a particular sport as a means, tool, or context for achieving some purpose or performing an activity.
  • E. usedInInternationalSportsAs
    Indicates that something serves as an official or recognized element (such as equipment, rules, or standards) within international-level sports competitions or activities.
  • 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_69f348dcf5d48190ac25b1365ae717a8 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6f8565134819096aac0175f924a9f completed May 3, 2026, 7:25 a.m.
PD Predicate disambiguation batch_69f6f65fd1d08190b88e5e68ba268500 completed May 3, 2026, 7:16 a.m.
Created at: April 30, 2026, 11:02 p.m.