Triple
T11409677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turnhouse Aerodrome |
E270334
|
entity |
| Predicate | primaryUseAfterWWII |
P5141
|
FINISHED |
| Object | civil airport for Edinburgh |
—
|
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: civil airport for Edinburgh | Statement: [Turnhouse Aerodrome, primaryUseAfterWWII, civil airport for Edinburgh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseAfterWWII Context triple: [Turnhouse Aerodrome, primaryUseAfterWWII, civil airport for Edinburgh]
-
A.
primaryUseLateWar
Indicates that something was used primarily during the later phase of a war, rather than in its early or middle stages.
-
B.
statusAfterWWII
chosen
Indicates the condition, role, or classification an entity had following the end of World War II.
-
C.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
D.
regionAfter1945
Indicates that one region exists as the geopolitical or administrative successor of another region after the year 1945.
-
E.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
- 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_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. |
Created at: April 8, 2026, 9:34 p.m.