Triple
T2740213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Howard Beach |
E60729
|
entity |
| Predicate | airportAccess |
P33519
|
FINISHED |
| Object | JFK Airport via Belt Parkway |
—
|
LITERAL 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: JFK Airport via Belt Parkway | Statement: [Howard Beach, airportAccess, JFK Airport via Belt Parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportAccess Context triple: [Howard Beach, airportAccess, JFK Airport via Belt Parkway]
-
A.
airportAccessMode
chosen
Indicates the typical mode or method of transportation used to access or reach an airport.
-
B.
airportStation
Indicates a location functions as an airport facility where air transport operations occur.
-
C.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
D.
airportRole
Indicates that an entity serves a specific functional role or capacity within the context of an airport.
-
E.
hasRunwayAccessVia
Indicates that an entity has access to a runway by means of a specified connecting route, facility, or intermediary.
- F. None of above.
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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb2da94c8190bc9d23262e3dfc07 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.