Triple
T28387083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bong Air Force Base (former) in Wisconsin |
E719046
|
entity |
| Predicate | plannedOpeningPeriod |
P174268
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Bong Air Force Base (former) in Wisconsin, plannedOpeningPeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedOpeningPeriod Context triple: [Bong Air Force Base (former) in Wisconsin, plannedOpeningPeriod, 1950s]
-
A.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
-
B.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
openingHoursCharacteristic
Indicates a relationship that specifies particular attributes or features of an entity’s opening hours, such as patterns, exceptions, or special conditions.
-
D.
openPeriod
Indicates that a specified time span is active or available for a particular activity, process, or state.
-
E.
temporarilyClosedFrom
Indicates that an entity is not accessible or operating for a specific, limited time period starting from a given point.
- F. None of above. chosen
Provenance (4 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
| PDg | Predicate description generation | batch_69f6bbf5a8288190ae170bcbe8ab65cf |
completed | May 3, 2026, 3:07 a.m. |
Created at: April 28, 2026, 1:11 a.m.