Triple

T36479512
Position Surface form Disambiguated ID Type / Status
Subject Michigan Stars FC E898769 entity
Predicate homeRivalryName P18267 FINISHED
Object Detroit metropolitan area soccer rivalry 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: Detroit metropolitan area soccer rivalry | Statement: [Michigan Stars FC, homeRivalryName, Detroit metropolitan area soccer rivalry]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: homeRivalryName
Context triple: [Michigan Stars FC, homeRivalryName, Detroit metropolitan area soccer rivalry]
  • A. hasLocalRivalryVenueWith
    Indicates that two entities share a venue or location where a local rivalry between them is regularly contested or expressed.
  • B. hasHomeStadiumInRivalry
    Indicates that one entity’s home stadium is the venue used when it participates in a rivalry with another entity.
  • C. countryOfRivalry
    Indicates that one entity is a country with which another entity has a relationship of rivalry or adversarial competition.
  • D. homeStadiumTeam
    Indicates that a particular stadium serves as the designated home venue for a specific sports team.
  • E. hasLocalRivalry chosen
    Indicates that there is an ongoing competitive or adversarial relationship between entities that are geographically close or share the same local area.
  • 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_69f76e5a0e088190a2b6706aeb41723c completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7be9d07ac8190adf796cbef60daf6 completed May 3, 2026, 9:31 p.m.
PD Predicate disambiguation batch_69f7bccf05bc8190b61fdb2b2a315811 completed May 3, 2026, 9:23 p.m.
Created at: May 3, 2026, 4:10 p.m.