Triple

T24108303
Position Surface form Disambiguated ID Type / Status
Subject Research Triangle E597288 entity
Predicate hasCollegeSportsRivalry P74502 FINISHED
Object Duke–UNC rivalry NE NERFINISHED

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: Duke–UNC rivalry | Statement: [Research Triangle, hasCollegeSportsRivalry, Duke–UNC rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCollegeSportsRivalry
Context triple: [Research Triangle, hasCollegeSportsRivalry, Duke–UNC rivalry]
  • A. hasRivalrySport
    Indicates a competitive relationship in which two entities are rivals specifically within the context of a sport or sporting activity.
  • B. conferenceRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
  • C. hasNationalRivalryContext
    Indicates that there exists a relationship of competitive or adversarial national rivalry between the associated entities, providing the contextual backdrop for their interaction or comparison.
  • D. associatedRivalry chosen
    Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
  • E. hasVarsityTeams
    Indicates that an institution fields official varsity-level sports teams.
  • 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_69e288c60f9c8190af948d7354aedbeb completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1de19057c819096a8b3290d33e2f6 completed April 29, 2026, 10:31 a.m.
PD Predicate disambiguation batch_69f17651458c8190bbfd301883e46085 completed April 29, 2026, 3:09 a.m.
Created at: April 17, 2026, 11:02 p.m.