Triple
T8314955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Fiscal Court of Germany |
E194682
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BFH |
E725540
|
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: BFH | Statement: [Federal Fiscal Court of Germany, abbreviation, BFH]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BFH Context triple: [Federal Fiscal Court of Germany, abbreviation, BFH]
-
A.
BFH
chosen
BFH is the abbreviation for Germany’s Federal Fiscal Court, the highest court for tax and customs law matters in the country.
-
B.
BF
BF is the IATA airline designator for French Bee, a French low-cost long-haul carrier.
-
C.
BF
BF is the two-letter ISO 3166-1 alpha-2 country code assigned to Burkina Faso.
-
D.
Bf
Bf is the aircraft designation prefix historically used for military aircraft designed or built by the German manufacturer Bayerische Flugzeugwerke, notably including early Messerschmitt fighters.
-
E.
BIF
BIF is the National Rail station code for Barrow-in-Furness railway station in Cumbria, England.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f540b2081908ccb1b2ed040c74e |
completed | March 31, 2026, 8:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc6eca6408190abc34286cb7e8085 |
completed | April 2, 2026, 1:31 a.m. |
Created at: March 30, 2026, 5:55 p.m.