Triple

T21077226
Position Surface form Disambiguated ID Type / Status
Subject CFA E519268 entity
Predicate hasISO4217Code P189 FINISHED
Object XOF NE NERFINISHED

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: XOF | Statement: [CFA, hasISO4217Code, XOF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: XOF
Context triple: [CFA, hasISO4217Code, XOF]
  • A. XOF chosen
    XOF is the West African CFA franc, a regional currency used by several West African countries including Niger.
  • B. XSF
    XSF is the nonprofit organization that develops and maintains the open XMPP communication protocols used for instant messaging and real-time communication.
  • C. OFB
    OFB is an Indian government organization that historically managed a network of ordnance factories responsible for producing arms, ammunition, and military equipment for the country's armed forces.
  • D. SXF
    SXF is the standard abbreviation used for the Sioux Falls Skyforce, a professional basketball team in the NBA G League.
  • E. SXF
    SXF was the IATA airport code for Berlin Schönefeld Airport, the former secondary international airport serving Berlin, Germany.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b506e59c8190849b71ed07929215 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e702d77b8081908ecfb05ab391fd39 completed April 21, 2026, 4:53 a.m.
Created at: April 16, 2026, 2:49 p.m.