Triple

T402447
Position Surface form Disambiguated ID Type / Status
Subject Washington Commanders–Philadelphia Eagles rivalry E9313 entity
Predicate relatedRivalry P8277 FINISHED
Object Dallas Cowboys–Washington Commanders rivalry 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: Dallas Cowboys–Washington Commanders rivalry | Statement: [Washington Commanders–Philadelphia Eagles rivalry, relatedRivalry, Dallas Cowboys–Washington Commanders rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relatedRivalry
Context triple: [Washington Commanders–Philadelphia Eagles rivalry, relatedRivalry, Dallas Cowboys–Washington Commanders rivalry]
  • A. hasRivalryEmotion
    Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
  • B. hasRivalryAspect chosen
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • C. divisionRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
  • D. rivalryName
    Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
  • E. foundedAsRivalOf
    Indicates that an entity was established specifically to compete with or challenge another entity.
  • 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_69a2e8004cb88190b92ed1add6abf41a completed Feb. 28, 2026, 1:05 p.m.
NER Named-entity recognition batch_69a2eca0e2048190a7bf360257965e56 completed Feb. 28, 2026, 1:24 p.m.
PD Predicate disambiguation batch_69a2e96ee4ec8190a5c0e3f491d3963d completed Feb. 28, 2026, 1:11 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.