Triple
T18326712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss Airport, Rygge |
E439027
|
entity |
| Predicate | openedForMilitaryUse |
P61587
|
FINISHED |
| Object | 1954 |
—
|
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: 1954 | Statement: [Moss Airport, Rygge, openedForMilitaryUse, 1954]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForMilitaryUse Context triple: [Moss Airport, Rygge, openedForMilitaryUse, 1954]
-
A.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
B.
openedToMilitaryTraffic
chosen
Indicates that a route, facility, or passage has been made accessible and available for use by military vehicles or operations.
-
C.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
D.
openedAsMilitaryAirfield
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
E.
openedForUseAs
Indicates that something was made available and began functioning in the capacity or role specified by another entity or purpose.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50aab3e7c81909b1c0a688707dfd6 |
completed | April 19, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69e44fe4ee10819086b4142444fca1f5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.