Triple

T4230982
Position Surface form Disambiguated ID Type / Status
Subject Minnesota Vikings–Detroit Lions rivalry E94579 entity
Predicate reasonForRivalry P43969 FINISHED
Object divisional 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: divisional opponents | Statement: [Minnesota Vikings–Detroit Lions rivalry, reasonForRivalry, divisional opponents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForRivalry
Context triple: [Minnesota Vikings–Detroit Lions rivalry, reasonForRivalry, divisional opponents]
  • A. rivalryBasis chosen
    Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
  • B. typeOfRivalry
    Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
  • C. hasRivalryEmotion
    Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
  • D. rivalryLevel
    Indicates the degree or intensity of competitive opposition or conflict between two entities.
  • E. divisionRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
  • 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_69b3453700a08190ae88792e3dc63207 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e62e3c881909ffb9269ba9018b9 completed March 12, 2026, 11:38 p.m.
PD Predicate disambiguation batch_69b347f3bd188190b0cd613e8a5c1683 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:05 p.m.