Triple
T38601534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slick Six |
E934227
|
entity |
| Predicate | hasLaunchPadDesignation |
P29508
|
FINISHED |
| Object | Space Launch Complex 6 |
—
|
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: Space Launch Complex 6 | Statement: [Slick Six, hasLaunchPadDesignation, Space Launch Complex 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchPadDesignation Context triple: [Slick Six, hasLaunchPadDesignation, Space Launch Complex 6]
-
A.
hasLaunchPadNumber
chosen
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
B.
hasLaunchPadsFor
Indicates that one entity provides or contains launch pads intended for use by another entity.
-
C.
hasLaunchPadType
Indicates that an entity (e.g., a launch facility or site) is associated with a specific type or classification of launch pad.
-
D.
designedToBeLaunchedFrom
Indicates that one entity is specifically created or configured for the purpose of being launched from another entity.
-
E.
hasHelipadDesignation
Indicates that an entity has been assigned a specific designation or identifier for its helipad.
- 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_69f76ecc17688190b389b693a5927501 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: May 3, 2026, 4:32 p.m.