Triple
T33212093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OLA |
E850187
|
entity |
| Predicate | hostSpacecraftLaunchSite |
P44497
|
FINISHED |
| Object | Cape Canaveral Air Force Station |
—
|
NE NERFINISHED |
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: Cape Canaveral Air Force Station | Statement: [OLA, hostSpacecraftLaunchSite, Cape Canaveral Air Force Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSpacecraftLaunchSite Context triple: [OLA, hostSpacecraftLaunchSite, Cape Canaveral Air Force Station]
-
A.
spaceLaunchDestination
Indicates the target location or body in space toward which a space launch is directed.
-
B.
launchSites
chosen
Indicates locations from which an object, mission, or vehicle is launched or initiated.
-
C.
nearbyLaunchComplex
Indicates that one launch complex is located close to another in physical space.
-
D.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
E.
spaceflightDestination
Indicates the target location or body in space that a spaceflight is intended to reach.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.