Triple
T490632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LaGuardia Airport |
E9979
|
entity |
| Predicate | hasThreeLetterCode |
P2569
|
FINISHED |
| Object | LGA |
E61301
|
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: LGA | Statement: [LaGuardia Airport, hasThreeLetterCode, LGA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LGA Context triple: [LaGuardia Airport, hasThreeLetterCode, LGA]
-
A.
LGA
chosen
LGA is the three-letter IATA airport code for LaGuardia Airport, a major commercial airport serving New York City.
-
B.
LAK
LAK is the standard abbreviation used to represent the Los Angeles Lakers NBA franchise in scores, statistics, and media.
-
C.
TGL
TGL is a tech-infused, primetime golf league co-founded by Tiger Woods and Rory McIlroy that features team-based competition in an indoor arena setting.
-
D.
LPC
The LPC is New York City’s official agency responsible for identifying, designating, and regulating the city’s landmarks and historic districts.
-
E.
LAL
LAL is the standard NBA abbreviation for the Los Angeles Lakers basketball franchise.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e22a308190b04d12974fd08a38 |
completed | Feb. 28, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a481ecd6e08190a091064a7a1d32c6 |
completed | March 1, 2026, 6:14 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.