Triple
T20724858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape May Airport |
E509406
|
entity |
| Predicate | opened as military facility |
P7893
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Cape May Airport, opened as military facility, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opened as military facility Context triple: [Cape May Airport, opened as military facility, 1943]
-
A.
openedAsMilitaryAirfield
chosen
Indicates that an airfield was originally established and began operation specifically for military aviation use.
-
B.
formerMilitaryBase
Indicates that a location was previously used as a military base but no longer serves that function.
-
C.
wasMilitaryBaseDuring
Indicates that a location functioned as a military base during a specified time period or event.
-
D.
isFormerMilitaryCenter
Indicates that a place previously served as a military center or base but no longer holds that function.
-
E.
wasMilitaryHeadquartersOf
Indicates that a place or facility served as the main command center or headquarters for a specific military force or organization.
- 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_69e0b4c4cc648190b45fda6e2b20af56 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1e662f08190917ee043612d413e |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:29 p.m.