Triple
T33081144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Cryogenic Second Stage |
E846509
|
entity |
| Predicate | launchSiteCompatibility |
P30131
|
FINISHED |
| Object | Cape Canaveral Space 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 Space Force Station | Statement: [Delta Cryogenic Second Stage, launchSiteCompatibility, Cape Canaveral Space Force Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchSiteCompatibility Context triple: [Delta Cryogenic Second Stage, launchSiteCompatibility, Cape Canaveral Space Force Station]
-
A.
launchSiteCode
Indicates the code that identifies the site or location from which a launch takes place.
-
B.
launchSites
Indicates locations from which an object, mission, or vehicle is launched or initiated.
-
C.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
-
D.
launchVehicleSupported
chosen
Indicates that one entity provides the necessary infrastructure, capability, or compatibility to support the operation or use of a particular launch vehicle.
-
E.
servesLaunchSite
Indicates that one entity functions as the launch site used by another entity for initiating launches.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:26 a.m.