Triple
T2864034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EWR |
E63393
|
entity |
| Predicate | otherMajorNYCAreaAirport |
P14083
|
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: [EWR, otherMajorNYCAreaAirport, LGA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LGA Context triple: [EWR, otherMajorNYCAreaAirport, LGA]
-
A.
LGA
chosen
LGA is the three-letter IATA airport code for LaGuardia Airport, a major commercial airport serving New York City.
-
B.
LBA
LBA is the IATA airport code for Leeds Bradford Airport, a regional international airport serving the cities of Leeds and Bradford in West Yorkshire, England.
-
C.
LGC
LGC is the three-letter IATA airport code for LaGrange–Callaway Airport in LaGrange, Georgia, United States.
-
D.
LAC
LAC refers to the Los Angeles Clippers, a professional NBA basketball team based in Los Angeles and a crosstown rival of the Los Angeles Lakers.
-
E.
LAK
LAK is the standard abbreviation used to represent the Los Angeles Lakers NBA franchise in scores, statistics, and media.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abe08ae5048190a0a3b573d9a5fdbc |
completed | March 7, 2026, 8:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b055e0c8088190a0fa67c9c14fc29b |
completed | March 10, 2026, 5:33 p.m. |
Created at: March 6, 2026, 10:02 p.m.