Triple
T37997059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC-40 |
E947987
|
entity |
| Predicate | hasLaunchRailOrMount |
P101263
|
FINISHED |
| Object | Falcon 9 launch mount |
—
|
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: Falcon 9 launch mount | Statement: [SLC-40, hasLaunchRailOrMount, Falcon 9 launch mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchRailOrMount Context triple: [SLC-40, hasLaunchRailOrMount, Falcon 9 launch mount]
-
A.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
B.
hasAccessoryRail
Indicates that an object is equipped with or includes an additional rail or mounting interface used to attach accessories.
-
C.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
D.
hasRail
chosen
Indicates that something is equipped with, includes, or is connected to a rail or rail system.
-
E.
hasLaunchPadType
Indicates that an entity (e.g., a launch facility or site) is associated with a specific type or classification of launch pad.
- 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_69f76efa37088190be5416b7ef1ca275 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:20 p.m.