Triple

T2894710
Position Surface form Disambiguated ID Type / Status
Subject New York Rangers–New Jersey Devils rivalry E63907 entity
Predicate fanBaseOverlap P43842 FINISHED
Object New York metropolitan area residents 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: New York metropolitan area residents | Statement: [New York Rangers–New Jersey Devils rivalry, fanBaseOverlap, New York metropolitan area residents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fanBaseOverlap
Context triple: [New York Rangers–New Jersey Devils rivalry, fanBaseOverlap, New York metropolitan area residents]
  • A. fanBaseInteraction
    Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
  • B. fanBase
    Indicates that one entity is the group of admirers or supporters devoted to another entity.
  • C. fanBaseScope
    Indicates the extent or range of people who are considered fans or followers of an entity.
  • D. fanBaseRelationship
    Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
  • E. fanBaseLocation
    Indicates the primary geographic area where an individual’s or group’s supporters or fans are predominantly located.
  • 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_69ab4c45822c8190830c5f2bb97bcfd0 completed March 6, 2026, 9:51 p.m.
NER Named-entity recognition batch_69abe063de6c8190bce9ddefd1dd62e1 completed March 7, 2026, 8:23 a.m.
PD Predicate disambiguation batch_69abdd17bcdc8190aa47274a50ba4ad4 completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abde0f4c648190b9812e64f30c39da completed March 7, 2026, 8:13 a.m.
Created at: March 6, 2026, 10:07 p.m.