Triple

T13869200
Position Surface form Disambiguated ID Type / Status
Subject France national rugby sevens team E333405 entity
Predicate governingBodyAbbreviation P2886 FINISHED
Object FFR E331928 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: FFR | Statement: [France national rugby sevens team, governingBodyAbbreviation, FFR]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FFR
Context triple: [France national rugby sevens team, governingBodyAbbreviation, FFR]
  • A. FFR chosen
    FFR is the commonly used abbreviation for the French Rugby Federation, the governing body for rugby union in France.
  • B. FFRRO
    FFRRO is a U.S. Environmental Protection Agency office that oversees the cleanup, restoration, and reuse of contaminated federal facilities such as military bases and government sites.
  • C. FRR
    FRR is the IATA airport code for Front Royal–Warren County Airport, a public airport serving the Front Royal area in Virginia, United States.
  • D. FFS
    FFS is the commonly used abbreviation for the Swiss Federal Railways, the national railway company of Switzerland.
  • E. FFS
    FFS is a high-performance file system originally developed for BSD Unix that introduced improved disk layout and efficiency over earlier Unix file systems.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de05c530148190b11704300bbd5f9b completed April 14, 2026, 9:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c70e48788190997562e045f3b014 completed May 3, 2026, 10:07 p.m.
Created at: April 9, 2026, 10:14 p.m.