Triple
T2864026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EWR |
E63393
|
entity |
| Predicate | FAA_LID |
P420
|
FINISHED |
| Object | EWR |
E63393
|
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: EWR | Statement: [EWR, FAA_LID, EWR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EWR Context triple: [EWR, FAA_LID, EWR]
-
A.
EWR
chosen
EWR is the three-letter IATA airport code for Newark Liberty International Airport, a major air travel hub serving the New York City metropolitan area.
-
B.
RWR
RWR is the abbreviation for the Royal Winnipeg Rifles, an infantry regiment of the Canadian Army Reserve based in Winnipeg, Manitoba.
-
C.
EYW
EYW is the IATA airport code for Key West International Airport, a small commercial airport serving Key West in the Florida Keys, USA.
-
D.
ERL
ERL is a research facility focused on studying and developing technologies for the exploration, monitoring, and management of Earth's natural resources.
-
E.
ERI
ERI is the Earthquake Research Institute of the University of Tokyo, a leading Japanese center for seismology and earthquake-related research.
- 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_69abdfb853908190aa2fd492e9fa5e87 |
completed | March 7, 2026, 8:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b01da030a88190b9e23a461695176f |
completed | March 10, 2026, 1:33 p.m. |
Created at: March 6, 2026, 10:02 p.m.