Triple
T36914691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EGPD |
E913012
|
entity |
| Predicate | associatedAirportHasHelicopterTraffic |
P99164
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [EGPD, associatedAirportHasHelicopterTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportHasHelicopterTraffic Context triple: [EGPD, associatedAirportHasHelicopterTraffic, true]
-
A.
hasHelicopterTraffic
chosen
Indicates that there is regular or notable helicopter movement or operations occurring in or over a given area or location.
-
B.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
C.
heliportType
Indicates the specific classification or category of a heliport based on its design, function, or operational characteristics.
-
D.
hasHelicopterTransferConnection
Indicates that there is a transfer connection between two locations or services that is specifically made by helicopter.
-
E.
hasHelipads
Indicates that an entity possesses one or more helipads available for helicopter landing and takeoff.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.