Triple
T32194105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City airspace |
E822352
|
entity |
| Predicate | containsHeliport |
P9476
|
FINISHED |
| Object | Downtown Manhattan Heliport |
—
|
NE NERFINISHED |
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: Downtown Manhattan Heliport | Statement: [New York City airspace, containsHeliport, Downtown Manhattan Heliport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsHeliport Context triple: [New York City airspace, containsHeliport, Downtown Manhattan Heliport]
-
A.
hasHeliport
chosen
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
B.
heliportType
Indicates the specific classification or category of a heliport based on its design, function, or operational characteristics.
-
C.
hasHelipads
Indicates that an entity possesses one or more helipads available for helicopter landing and takeoff.
-
D.
containsAirfield
Indicates that a location or area includes at least one airfield within its boundaries.
-
E.
hasHelipadDesignation
Indicates that an entity has been assigned a specific designation or identifier for its helipad.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffc083a54c8190ac80d05ee8d20a6b |
completed | May 9, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69ffbfeb05b88190b4d50ce8124004d9 |
completed | May 9, 2026, 11:14 p.m. |
Created at: May 1, 2026, 12:35 a.m.