Triple
T17026384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSVO |
E413074
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FSVO |
E413074
|
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: FSVO | Statement: [FSVO, abbreviation, FSVO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FSVO Context triple: [FSVO, abbreviation, FSVO]
-
A.
FSVO
chosen
FSVO is the Swiss federal authority responsible for overseeing food safety, animal health, and animal welfare in Switzerland.
-
B.
FSV
FSV is the commonly used abbreviation for FSV Zwickau, a German football club based in Zwickau, Saxony.
-
C.
VOI
VOI is the ICAO airline designator used to identify Volaris, a Mexican low-cost carrier, in aviation operations and communications.
-
D.
FSO
FSO is the Swiss federal authority responsible for collecting, analyzing, and publishing national statistics on the country’s population, economy, and society.
-
E.
FSO
FSO is Russia’s Federal Protective Service, the powerful security agency responsible for protecting top state officials and key government facilities.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d5ed388190871aa738cac04b65 |
completed | April 18, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b53306081908972a0a5db474b6c |
completed | May 10, 2026, 11:57 p.m. |
Created at: April 10, 2026, 5:33 a.m.