Triple
T23270050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Luis Obispo County Regional Airport |
E588262
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | SBP |
E1577172
|
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: SBP | Statement: [San Luis Obispo County Regional Airport, FAA LID, SBP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SBP Context triple: [San Luis Obispo County Regional Airport, FAA LID, SBP]
-
A.
SBP
SBP is the National Rail station code for Stonebridge Park railway station in northwest London, England.
-
B.
SBP
SBP is a federally assisted meal program in the United States that provides nutritious breakfasts to schoolchildren to support their health and learning.
-
C.
SBP
SBP is the central bank of Pakistan, responsible for regulating the country’s monetary and credit system and ensuring financial stability.
-
D.
SBP
chosen
SBP is the IATA airport code for San Luis Obispo County Regional Airport, a commercial airport serving San Luis Obispo and California’s Central Coast region.
-
E.
SBSP
SBSP is the ICAO airport code for Congonhas–São Paulo Airport, a major domestic airport serving the city of São Paulo, Brazil.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957324bc8190b8b53d4b18386151 |
completed | April 29, 2026, 5:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c4c86b1408190915e18bd59d7791e |
completed | May 19, 2026, 11:41 a.m. |
Created at: April 17, 2026, 4:45 p.m.