Triple
T16432159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 541 (via Perseverance rover) |
E399093
|
entity |
| Predicate | solidRocketBoostersCount |
P44184
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Atlas V 541 (via Perseverance rover), solidRocketBoostersCount, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solidRocketBoostersCount Context triple: [Atlas V 541 (via Perseverance rover), solidRocketBoostersCount, 4]
-
A.
numberOfSolidRocketBoosters
chosen
Indicates the quantity of solid rocket boosters associated with a given launch vehicle or spacecraft configuration.
-
B.
solidRocketBoosters
Indicates that an entity is equipped with or uses solid rocket boosters as part of its propulsion system.
-
C.
numberOfBoostersPerLaunch
Indicates the quantity of boosters used in each individual launch.
-
D.
solidRocketBoosterSupplier
Indicates that one entity serves as a supplier of solid rocket boosters to another entity.
-
E.
solidRocketBoosterManufacturer
Indicates that one entity is the manufacturer responsible for producing the solid rocket booster used by another entity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.