Triple

T294784
Position Surface form Disambiguated ID Type / Status
Subject Dallas Cowboys–Philadelphia Eagles rivalry E6068 entity
Predicate rivalryRootCause P903 FINISHED
Object divisional competition 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: divisional competition | Statement: [Dallas Cowboys–Philadelphia Eagles rivalry, rivalryRootCause, divisional competition]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rivalryRootCause
Context triple: [Dallas Cowboys–Philadelphia Eagles rivalry, rivalryRootCause, divisional competition]
  • A. divisionRivalry chosen
    Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
  • B. rivalryName
    Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
  • C. hasRivalryEmotion
    Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
  • D. foundedAsRivalOf
    Indicates that an entity was established specifically to compete with or challenge another entity.
  • E. rivalryCharacterization
    Indicates a relationship in which two entities are characterized as rivals, typically defined by ongoing competition, opposition, or conflict between them.
  • 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_69a2e79114b081909490b3bf5a5dbb51 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2e9e273f88190ac5355d1310376ed completed Feb. 28, 2026, 1:13 p.m.
PD Predicate disambiguation batch_69a2e9368894819093eeae4347dfcc5a completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:06 p.m.