Triple
T5498875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Federal Roads Office |
E144276
|
entity |
| Predicate | usesAbbreviation |
P43
|
FINISHED |
| Object | OFROU |
E531331
|
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: OFROU | Statement: [Swiss Federal Roads Office, usesAbbreviation, OFROU]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OFROU Context triple: [Swiss Federal Roads Office, usesAbbreviation, OFROU]
-
A.
OFROU
chosen
OFROU is the Swiss Federal Roads Office, the national authority responsible for planning, constructing, and maintaining Switzerland’s national road network and related traffic policies.
-
B.
FRO
FRO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Faroe Islands.
-
C.
OFR
OFR is a U.S. Treasury Department bureau that collects and analyzes financial data to support oversight of the stability of the financial system.
-
D.
OFU
OFU is the IATA airport code for Ofu Airport, a small airfield serving the island of Ofu in American Samoa.
-
E.
Foor
Foor is an alternative name for the Fur language spoken by the Fur people of western Sudan.
- 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01b9050d08190b0cfcfdb5d414476 |
completed | March 22, 2026, 4:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c04c9c78308190935c3fbbaff08b70 |
completed | March 22, 2026, 8:10 p.m. |
Created at: March 22, 2026, 3:32 p.m.