Triple
T21328646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fürstenfeldbruck |
E525834
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | FFB |
—
|
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: FFB | Statement: [Fürstenfeldbruck, vehicleRegistrationCode, FFB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FFB Context triple: [Fürstenfeldbruck, vehicleRegistrationCode, FFB]
-
A.
FFB
chosen
FFB is the vehicle registration code used for the Fürstenfeldbruck district in Bavaria, Germany.
-
B.
FBB
FBB is the operating company responsible for managing Berlin Brandenburg Airport and related airport facilities in the Berlin region.
-
C.
FBBE
FBBE is the regulatory body responsible for overseeing bar admissions and character and fitness evaluations for prospective lawyers in the state of Florida.
-
D.
FFS
FFS is the state agency responsible for managing and protecting Florida’s forest resources, including wildfire prevention, suppression, and sustainable forestry.
-
E.
FFS
FFS is the commonly used abbreviation for the Swiss Federal Railways, the national railway company of Switzerland.
- 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_69e0b51b90788190a4dd823d962626da |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7ab4e88848190b6efe85a4c8cd85a |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 16, 2026, 4:42 p.m.