Triple
T2843152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston Logan International Airport |
E62516
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | BOS |
E48656
|
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: BOS | Statement: [Boston Logan International Airport, FAAcode, BOS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BOS Context triple: [Boston Logan International Airport, FAAcode, BOS]
-
A.
BOS
BOS is the standard three-letter abbreviation used to represent the Boston Braves of the American Hockey League.
-
B.
BOS
chosen
BOS is the three-letter IATA airport code for Boston Logan International Airport, the primary airport serving the Boston, Massachusetts area.
-
C.
Boston T
Boston T is the public rapid transit system serving the Greater Boston area, operated by the Massachusetts Bay Transportation Authority (MBTA).
-
D.
BOL
BOL is the three-letter ISO 3166-1 alpha-3 country code assigned to Bolivia.
-
E.
Beantown
Beantown is a popular nickname for the city of Boston, Massachusetts, often used in informal and cultural references to the 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1898748190b031a2bd2091c0c0 |
completed | March 7, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b01d7c84e8819098089bd1c6874189 |
completed | March 10, 2026, 1:32 p.m. |
Created at: March 6, 2026, 10:01 p.m.