Triple
T4528999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inverness Airport |
E106247
|
entity |
| Predicate | civilOperationsBegan |
P11439
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [Inverness Airport, civilOperationsBegan, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilOperationsBegan Context triple: [Inverness Airport, civilOperationsBegan, 1947]
-
A.
beganCivilOperations
chosen
Indicates that an entity initiated or commenced civil (non-military) administrative or operational activities in relation to another entity or context.
-
B.
civilWarStart
Indicates the point in time or event at which an internal armed conflict between factions of the same state or society begins.
-
C.
peacetimeOperation
Indicates that an entity is engaged in activities or functions carried out under normal, non-wartime conditions.
-
D.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
E.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd5779593081908593537b9239e01b |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.