Triple
T12844339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concourse C2 |
E307132
|
entity |
| Predicate | airportCode |
P418
|
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: [Concourse C2, airportCode, EWR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EWR Context triple: [Concourse C2, airportCode, 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.
EWE
EWE is the National Rail station code for Ewell West railway station in Surrey, England.
-
C.
WRR
WRR is the commonly used abbreviation for the Western Recruiting Region, a U.S. military administrative area responsible for managing recruitment activities across the western United States.
-
D.
RWR
RWR is the abbreviation for the Royal Winnipeg Rifles, an infantry regiment of the Canadian Army Reserve based in Winnipeg, Manitoba.
-
E.
ELW
ELW is the National Rail station code for Eltham railway station in the London Borough of Greenwich, England.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96ff3a7208190b93f6292ed5efc07 |
completed | April 10, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b9fa40c8190bbc2c6ad22795de4 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:36 p.m.