Triple
T32831073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron launch vehicle |
E839689
|
entity |
| Predicate | launchFrequencyGoal |
P159806
|
FINISHED |
| Object | high-cadence commercial launches |
—
|
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: high-cadence commercial launches | Statement: [Electron launch vehicle, launchFrequencyGoal, high-cadence commercial launches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchFrequencyGoal Context triple: [Electron launch vehicle, launchFrequencyGoal, high-cadence commercial launches]
-
A.
frequencyGoal
chosen
Indicates the intended or target rate at which an action, event, or behavior should occur over a given time period.
-
B.
launchCostGoal
Indicates a target or intended cost level associated with launching something (e.g., a product, project, or mission).
-
C.
laterFrequency
Indicates that one event, state, or action occurs with a lower frequency than another in a temporal sequence.
-
D.
goalNumber
Indicates that an entity is associated with a specific target or objective quantified as a number.
-
E.
numberPerLaunch
Indicates the quantity of items or units associated with each individual launch event.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 1:16 a.m.