Triple
T11409595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Airport |
E270332
|
entity |
| Predicate | hasHelicopterTraffic |
P99164
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Edinburgh Airport, hasHelicopterTraffic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHelicopterTraffic Context triple: [Edinburgh Airport, hasHelicopterTraffic, yes]
-
A.
hasHeliport
Indicates that an entity possesses or is equipped with a heliport facility for helicopter landing and takeoff.
-
B.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
C.
isHelicopterOnly
Indicates that the subject is restricted to or designated exclusively for use by helicopters.
-
D.
hasHelicopterTrainingRole
Indicates that an entity holds a role or position specifically related to the training or instruction of helicopter operations.
-
E.
hasCruiseTraffic
Indicates that there is cruise ship traffic occurring at or involving a particular location or route.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8014e72748190a01bde2f0105cedb |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
| PDg | Predicate description generation | batch_69d80010712c819089ea2e31e664abe1 |
completed | April 9, 2026, 7:37 p.m. |
Created at: April 8, 2026, 9:34 p.m.