Triple
T18712235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rocky Mount–Wilson Regional Airport |
E457544
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | RWI |
E1338629
|
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: RWI | Statement: [Rocky Mount–Wilson Regional Airport, FAA LID, RWI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RWI Context triple: [Rocky Mount–Wilson Regional Airport, FAA LID, RWI]
-
A.
RWI
chosen
RWI is the three-letter IATA airport code for Rocky Mount–Wilson Regional Airport in North Carolina, United States.
-
B.
GWI
GWI is the National Rail station code for Greenwich railway station in London, England.
-
C.
WIS
WIS is the standard abbreviation used for the Wisconsin Woodchucks baseball team.
-
D.
WIS
WIS is the World Meteorological Organization’s global information system for sharing and distributing meteorological, hydrological, and related environmental data.
-
E.
WIS
WIS is the vehicle registration code used on license plates for the district of Nordwestmecklenburg in the German state of Mecklenburg-Vorpommern.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5671c53988190bfc132c853cebd02 |
completed | April 19, 2026, 11:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0532503674819092eb1b83bf3289bd |
completed | May 14, 2026, 2:24 a.m. |
Created at: April 10, 2026, 11:50 a.m.