Triple
T34883750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal C concourses at EWR |
E1006082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | airport concourse complex |
C10703
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: airport concourse complex Context triple: [Terminal C concourses at EWR, instanceOf, airport concourse complex]
-
A.
former airport terminal concourse
A former airport terminal concourse is a decommissioned passenger circulation and gate area once used for boarding, disembarking, and connecting flights, now repurposed or left inactive.
-
B.
passenger terminal concourse
chosen
A passenger terminal concourse is a large, central circulation space within a transport terminal where travelers move between entrances, ticketing, security, and boarding areas, often containing seating, retail, and information services.
-
C.
airport lounge
An airport lounge is a designated, often exclusive area within an airport that offers travelers a comfortable place to relax, work, and access amenities such as seating, refreshments, Wi‑Fi, and sometimes showers or business services while waiting for their flights.
-
D.
airport-related building
A building located on or near an airport that supports air travel operations, such as terminals, control towers, hangars, or maintenance facilities.
-
E.
international terminal area
An international terminal area is a designated section of an airport where passengers check in, depart, arrive, and transit for international flights, including associated facilities such as customs, immigration, security, and boarding gates.
- F. None of above.
Provenance (1 batch)
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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.