Triple

T3339726
Position Surface form Disambiguated ID Type / Status
Subject Denver Broncos–Kansas City Chiefs rivalry E70226 entity
Predicate isConsideredLongStanding P17938 FINISHED
Object yes 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: yes | Statement: [Denver Broncos–Kansas City Chiefs rivalry, isConsideredLongStanding, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isConsideredLongStanding
Context triple: [Denver Broncos–Kansas City Chiefs rivalry, isConsideredLongStanding, yes]
  • A. hasLongTermDatasetSince
    Indicates that an entity has maintained or used a particular dataset continuously starting from a specified point in time.
  • B. isLongRunning chosen
    Indicates that an action, process, or operation continues for an extended duration, typically longer than is usual or expected.
  • C. isPermanentForMembers
    Indicates that a condition, status, or setting is unchangeable and remains in effect indefinitely for the members it applies to.
  • D. isDormant
    Indicates that an entity is currently inactive or in a resting state, with its usual functions or activities temporarily suspended.
  • E. hasAdministrativeStatusSince
    Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
  • 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_69ad85a405e48190b6e68de7cf9f319e completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb1bf1f648190993ac8e9dda60983 completed March 8, 2026, 5:28 p.m.
PD Predicate disambiguation batch_69ada42c2ba8819091136805ce17b39d completed March 8, 2026, 4:30 p.m.
Created at: March 8, 2026, 3:12 p.m.