Triple
T6121472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 1 (JFK) |
E136492
|
entity |
| Predicate | isLocatedAtAirportType |
P68256
|
FINISHED |
| Object | major international hub airport |
—
|
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: major international hub airport | Statement: [Terminal 1 (JFK), isLocatedAtAirportType, major international hub airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLocatedAtAirportType Context triple: [Terminal 1 (JFK), isLocatedAtAirportType, major international hub airport]
-
A.
airportLocatedWithin
Indicates that an airport is geographically situated inside the boundaries of a specified area or region.
-
B.
hasStationAtAirport
Indicates that an organization or service operates a station or facility located at a specific airport.
-
C.
isPublicAirport
Indicates that an airport is open for use by the general public rather than restricted to private or military operations.
-
D.
appliesToAirport
Indicates that something is relevant, valid, or specifically intended for use at a particular airport.
-
E.
airportLocatedIn
Indicates that an airport is geographically situated within a specific administrative or territorial area.
- F. None of above. chosen
Provenance (4 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bf16ad48190958cc46510e02bd3 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.