Triple

T20941671
Position Surface form Disambiguated ID Type / Status
Subject Figari–Sud Corse Airport E515735 entity
Predicate hasCode P9567 FINISHED
Object FSC 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: FSC | Statement: [Figari–Sud Corse Airport, hasCode, FSC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FSC
Context triple: [Figari–Sud Corse Airport, hasCode, FSC]
  • A. FSC chosen
    FSC is the IATA airport code for Figari–Sud Corse Airport, a regional airport serving the southern part of Corsica, France.
  • B. FSC
    FSC is the primary South Korean government regulator overseeing financial policy, markets, and institutions.
  • C. FSC
    FSC is the post-nominal abbreviation used by members of the De La Salle Brothers, a Catholic religious teaching congregation.
  • D. FSC Taiwan
    FSC Taiwan is the government agency responsible for overseeing and regulating Taiwan’s financial services sector, including banking, securities, futures, and insurance.
  • E. FSC Troika
    FSC Troika is a rotating leadership group within the OSCE Forum for Security Co-operation that helps guide and coordinate its security and arms control agenda.
  • 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f955f0148190ae42278ad5c0f363 completed April 21, 2026, 4:13 a.m.
Created at: April 16, 2026, 12:50 p.m.