Triple
T497837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Air Force Academy Cadet Chapel |
E10333
|
entity |
| Predicate | designPeriod |
P14397
|
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: [US Air Force Academy Cadet Chapel, designPeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPeriod Context triple: [US Air Force Academy Cadet Chapel, designPeriod, 1950s]
-
A.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
-
B.
designDate
Indicates the date on which something was originally designed or its design was completed.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
currentDesignInForceSince
Indicates the date or point in time from which the current design has been officially in effect or valid.
-
E.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1183e988190bce70932a9678134 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edfa87cc8190a77c726a5a55b7d9 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eebbd70481908b462296671de67b |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.