Triple
T13105473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FedBizOpps |
E310831
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | FBO |
E310830
|
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: FBO | Statement: [FedBizOpps, abbreviation, FBO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: FBO Context triple: [FedBizOpps, abbreviation, FBO]
-
A.
FBO
FBO, short for Film Booking Offices of America, was a 1920s American film distribution and production company that later became part of RKO Pictures.
-
B.
FFB
FFB is the vehicle registration code used for the Fürstenfeldbruck district in Bavaria, Germany.
-
C.
FBX
FBX is a widely used 3D asset exchange file format that supports complex geometry, materials, animation, and scene data across various graphics and game development applications.
-
D.
FBO.gov
chosen
FBO.gov was the former U.S. federal government’s primary online portal for posting and searching federal procurement and contracting opportunities.
-
E.
FBB
FBB is the operating company responsible for managing Berlin Brandenburg Airport and related airport facilities in the Berlin region.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98154c9f48190aeca779d97151759 |
completed | April 10, 2026, 11:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6e27a325c8190a5c0f1a582340078 |
completed | May 3, 2026, 5:51 a.m. |
Created at: April 9, 2026, 9:05 p.m.