Triple

T14218128
Position Surface form Disambiguated ID Type / Status
Subject Notre Dame Fighting Irish baseball E352412 entity
Predicate hasHistoricRivalries P22384 FINISHED
Object historic rivalries in college baseball 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: historic rivalries in college baseball | Statement: [Notre Dame Fighting Irish baseball, hasHistoricRivalries, historic rivalries in college baseball]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricRivalries
Context triple: [Notre Dame Fighting Irish baseball, hasHistoricRivalries, historic rivalries in college baseball]
  • A. hasHistoricRivalry chosen
    Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
  • B. hasRivalryRoot
    Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
  • C. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • D. associatedRivalry
    Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
  • 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_69d8278a06e481908b5d6af0a8afe737 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de621258d4819085f358cd2cf109e4 completed April 14, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69de05bcd7d48190a4848d9320404aa6 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:06 a.m.