Triple
T4860374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wall Street Heliport |
E108642
|
entity |
| Predicate | hasNumberOfHelipads |
P5946
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Wall Street Heliport, hasNumberOfHelipads, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfHelipads Context triple: [Wall Street Heliport, hasNumberOfHelipads, 1]
-
A.
hasHelipads
chosen
Indicates that an entity possesses one or more helipads available for helicopter landing and takeoff.
-
B.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
C.
hasPrivateHelipad
Indicates that an entity possesses and controls a helipad that is designated for private, non-public use.
-
D.
hasEmergencyAirstrip
Indicates that an entity possesses or includes an airstrip specifically designated and equipped for emergency use.
-
E.
hasMilitaryRamp
Indicates that a structure or location is equipped with a ramp specifically designed for military use, such as loading, unloading, or deploying military personnel, vehicles, or equipment.
- 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_69bd440b965081908b0557721cae6338 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6d5e247c8190b6ae4e9b529f0345 |
completed | March 20, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69bd6c27334481909ba8ac80854f7d8e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:26 p.m.