Triple
T29323052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SpinLaunch |
E743562
|
entity |
| Predicate | publiclyDiscussedChallenge |
P82614
|
FINISHED |
| Object | aerodynamic heating on payload |
—
|
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: aerodynamic heating on payload | Statement: [SpinLaunch, publiclyDiscussedChallenge, aerodynamic heating on payload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publiclyDiscussedChallenge Context triple: [SpinLaunch, publiclyDiscussedChallenge, aerodynamic heating on payload]
-
A.
challengeFor
Indicates that one entity presents a difficulty, test, or obstacle that must be faced or overcome by another entity.
-
B.
relatedChallenge
Indicates that one challenge is connected to another challenge, such as being similar, dependent, or otherwise contextually linked.
-
C.
challengeTo
Indicates that one entity issues a challenge or dare for another entity to face or respond to.
-
D.
challengeType
Indicates the specific category or kind of challenge associated with an action or relationship between entities.
-
E.
discussionPublic
chosen
Indicates that a discussion is accessible to the general public rather than being restricted or private.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 28, 2026, 1:24 p.m.