Triple

T15468175
Position Surface form Disambiguated ID Type / Status
Subject Arizona State Sun Devils women's gymnastics E372084 entity
Predicate hasRegionalRivalry P80695 FINISHED
Object Pac-12 regional opponents 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: Pac-12 regional opponents | Statement: [Arizona State Sun Devils women's gymnastics, hasRegionalRivalry, Pac-12 regional opponents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRegionalRivalry
Context triple: [Arizona State Sun Devils women's gymnastics, hasRegionalRivalry, Pac-12 regional opponents]
  • A. hasLocalRivalry
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • B. rivalryRegion chosen
    Indicates a competitive or adversarial relationship that exists between entities within a specific geographic or regional context.
  • C. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • D. hasRivalryRoot
    Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
  • E. hasRivalryContext
    Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
  • 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_69d85cc8bd308190886949510b42e764 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f69a31c81909a749247b6615d91 completed April 16, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69ded284bd008190b31c53b4f1cebadd completed April 14, 2026, 11:49 p.m.
Created at: April 10, 2026, 3:33 a.m.