Triple

T13087314
Position Surface form Disambiguated ID Type / Status
Subject Florida Derby E310369 entity
Predicate hasRivalryNarrative P72886 FINISHED
Object state supremacy in Florida soccer 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: state supremacy in Florida soccer | Statement: [Florida Derby, hasRivalryNarrative, state supremacy in Florida soccer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRivalryNarrative
Context triple: [Florida Derby, hasRivalryNarrative, state supremacy in Florida soccer]
  • A. hasRivalryAspect
    Indicates that there exists a competitive or adversarial relationship or dimension between entities.
  • B. hasRivalryContext chosen
    Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
  • C. hasRivalryEmotion
    Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
  • D. hasRivalryRoot
    Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
  • E. hasHistoricRivalry
    Indicates a long-standing, often competitive or adversarial relationship between two entities, typically rooted in significant past conflicts or repeated opposition.
  • 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_69d806a733548190989cfd4ce981ca33 completed April 9, 2026, 8:05 p.m.
NER Named-entity recognition batch_69d981378dd08190b4f00e4e5df0e480 completed April 10, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69d9803f6c508190bfadfbc2d00c2c64 completed April 10, 2026, 10:57 p.m.
Created at: April 9, 2026, 9:02 p.m.