Triple

T3514930
Position Surface form Disambiguated ID Type / Status
Subject USL Super League E74282 entity
Predicate targetSanctioningLevel P45060 FINISHED
Object Division I 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: Division I | Statement: [USL Super League, targetSanctioningLevel, Division I]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetSanctioningLevel
Context triple: [USL Super League, targetSanctioningLevel, Division I]
  • A. sanctioningLevel chosen
    Indicates the degree or severity of formal penalties, restrictions, or disciplinary measures imposed in response to a violation or noncompliant behavior.
  • B. canBeSanctionedFor
    Indicates that an entity is subject to penalties or disciplinary measures as a consequence of a specified action, behavior, or condition.
  • C. typeOfSanction
    Indicates the specific category or kind of sanction that is applied in a given situation.
  • D. requiresSanctioningBody
    Indicates that an action, event, or decision must be approved or authorized by a designated sanctioning authority or governing body.
  • E. requiresSanctioningBodyRecognition
    Indicates that an entity’s validity, operation, or status is contingent upon being formally recognized by an authorized sanctioning body.
  • 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_69ad85cfb5c881909c9a2edd9d6043cc completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adbc2efa4c8190ac1ca221f3f0eba4 completed March 8, 2026, 6:13 p.m.
PD Predicate disambiguation batch_69adae10689c8190b7dc6d7daa8295b6 completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:19 p.m.