Triple
T21098318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster Airport (Pennsylvania) |
E519826
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | LNS |
—
|
NE NERFINISHED |
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: LNS | Statement: [Lancaster Airport (Pennsylvania), FAA LID, LNS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LNS Context triple: [Lancaster Airport (Pennsylvania), FAA LID, LNS]
-
A.
LNS
LNS is the commonly used abbreviation for the Laboratory for Nuclear Science, a research institution focused on advancing the understanding of nuclear and particle physics.
-
B.
LNS
LNS is the commonly used abbreviation for Lindsey Nelson Stadium, the University of Tennessee’s baseball venue in Knoxville.
-
C.
LNS
chosen
LNS is the three-letter IATA airport code for Lancaster Airport in Lancaster County, Pennsylvania, serving regional air traffic.
-
D.
LNZ
LNZ is the IATA airport code for Linz Airport, the main international airport serving the city of Linz in Austria.
-
E.
LNI
LNI is the ICAO airline designator used for Lion Air, a major Indonesian low-cost carrier.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b508d8dc81909be940dafe36c8f7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e71b5a3a9481908e30fba9717dc461 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 2:52 p.m.