Triple
T8496818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSF |
E201119
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | BSF |
E201119
|
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: BSF | Statement: [BSF, abbreviation, BSF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BSF Context triple: [BSF, abbreviation, BSF]
-
A.
BSF
BSF (Bootstrapping Server Function) is a 3GPP network element that manages authentication bootstrapping and key distribution to enable secure access to IP-based multimedia and data services.
-
B.
BSF
chosen
BSF is India’s primary border guarding organization responsible for securing the country’s land borders during both peace and wartime.
-
C.
BSB
BSB is the commonly used abbreviation for the Bar Standards Board, the regulatory body for barristers and specialised legal services in England and Wales.
-
D.
BSB
BSB is the railway station code for Varanasi Junction, a major rail hub in the Indian state of Uttar Pradesh.
-
E.
BSB
BSB is the IATA airport code for Brasília International Airport, the main air gateway serving Brazil’s capital city.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe57f8c508190b3a93ef180db9873 |
completed | March 31, 2026, 3:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce4e01e65481908b868d1810a83e0e |
completed | April 2, 2026, 11:07 a.m. |
Created at: March 30, 2026, 6:13 p.m.