Triple
T8673556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaceport Cornwall |
E205858
|
entity |
| Predicate | hasLaunchType |
P33533
|
FINISHED |
| Object | horizontal launch |
—
|
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: horizontal launch | Statement: [Spaceport Cornwall, hasLaunchType, horizontal launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchType Context triple: [Spaceport Cornwall, hasLaunchType, horizontal launch]
-
A.
hasLaunchContext
Indicates that an entity is associated with a specific situation, environment, or set of conditions under which it is initiated or launched.
-
B.
hasLaunchedFor
Indicates that an entity (such as a product, feature, or service) has been officially released or made available specifically for another entity (such as a user, group, market, or platform).
-
C.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
D.
hasLaunchHistoryEvent
Indicates that there exists a recorded event in the launch history associated with the given entity.
-
E.
launchedVia
chosen
Indicates that an entity is initiated, deployed, or started by means of a specified method, mechanism, or intermediary.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:31 p.m.