Triple
T18001122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lewiston–Nez Perce County Airport |
E430628
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | LWS |
—
|
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: LWS | Statement: [Lewiston–Nez Perce County Airport, IATAcode, LWS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LWS Context triple: [Lewiston–Nez Perce County Airport, IATAcode, LWS]
-
A.
LWS
chosen
LWS is the IATA airport code for the regional airport serving Lewiston, Idaho.
-
B.
LWS
LWS is the scene file format used by the LightWave 3D software to store information about objects, animation, cameras, and lights in a 3D project.
-
C.
LWS
LWS is the three-letter National Rail station code for Lewes railway station in East Sussex, England.
-
D.
LWS
LWS is the Long Wavelength Spectrometer, a far-infrared observing instrument that flew aboard the European Space Agency’s Infrared Space Observatory.
-
E.
LWP
LWP is the abbreviation for the Polish People’s Army, the communist-era armed forces of Poland that existed from the end of World War II until 1989.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b3e82ca48190aeb53e03c95ef223 |
completed | April 19, 2026, 10:52 a.m. |
Created at: April 10, 2026, 10:23 a.m.