Triple
T19418008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cornwall Airport Newquay |
E485770
|
entity |
| Predicate | hasMilitaryOrigin |
P40599
|
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: [Cornwall Airport Newquay, hasMilitaryOrigin, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryOrigin Context triple: [Cornwall Airport Newquay, hasMilitaryOrigin, true]
-
A.
militaryOrigin
chosen
Indicates that an entity originates from, was created by, or is derived from a military organization, context, or background.
-
B.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
C.
derivedFromMilitaryOrCivil
Indicates that something originates from, is based on, or is obtained through military or civil (non-military governmental) sources, activities, or contexts.
-
D.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
-
E.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62afad8d881908f1de6324e55d2f6 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.