Triple

T14611888
Position Surface form Disambiguated ID Type / Status
Subject RFO Sat E342980 entity
Predicate hasAbbreviation P43 FINISHED
Object RFO Sat E342980 NE 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: RFO Sat | Statement: [RFO Sat, hasAbbreviation, RFO Sat]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFO Sat
Context triple: [RFO Sat, hasAbbreviation, RFO Sat]
  • A. RFO Sat chosen
    RFO Sat was a French television channel that broadcast programming for France’s overseas departments and territories before being rebranded as France Ô.
  • B. RFS
    RFS is the commonly used abbreviation for the Russian Football Union, the governing body of football in Russia.
  • C. SB RF
    SB RF is the commonly used abbreviation for the Security Council of the Russian Federation, a key governmental body responsible for national security and strategic policy.
  • D. SRSO
    SRSO is the commonly used abbreviation for the Swedish Radio Symphony Orchestra, one of Sweden’s leading professional orchestras based in Stockholm.
  • E. SRFC
    SRFC is the commonly used abbreviation for Sacramento Republic FC, a professional soccer club based in Sacramento, California.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822dec68081908c2553145c4051dc completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb450e6588190a94488d8e71888c8 completed April 14, 2026, 9:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69fda91f437c8190ada4d1c3708faedd completed May 8, 2026, 9:13 a.m.
Created at: April 10, 2026, 1:25 a.m.