Triple

T27174861
Position Surface form Disambiguated ID Type / Status
Subject URI Rams men's basketball E683015 entity
Predicate notableRivalryType P200641 FINISHED
Object regional rivalries in New England 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: regional rivalries in New England | Statement: [URI Rams men's basketball, notableRivalryType, regional rivalries in New England]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableRivalryType
Context triple: [URI Rams men's basketball, notableRivalryType, regional rivalries in New England]
  • A. notableRivalry
    Indicates a significant, well-recognized competitive or adversarial relationship between two entities.
  • B. notableRivalryElement
    Indicates that one entity is a significant component, example, or instance within a notable rivalry between two or more entities.
  • C. nicknameOfRivalryBetween
    Indicates that one entity is a nickname or informal title used to refer to a particular rivalry between other entities.
  • D. isMajorRivalryFor
    Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
  • E. conferenceRivalry
    Indicates a competitive or adversarial relationship between entities that belong to the same conference or organized grouping.
  • F. None of above. chosen

Provenance (4 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_69eefad086808190ab89816c0c300476 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69ff9d9cb4f8819083682be3c483b599 completed May 9, 2026, 8:48 p.m.
PD Predicate disambiguation batch_69ff9c38bf9c8190bbb85b32f3ae3d2e completed May 9, 2026, 8:42 p.m.
PDg Predicate description generation batch_69ff9d9ba1ac8190a0cca5764bb5904d completed May 9, 2026, 8:48 p.m.
Created at: April 27, 2026, 9:25 a.m.