Triple
T21307645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas V 421 |
E525240
|
entity |
| Predicate | configurationFeatures |
P143676
|
FINISHED |
| Object | 4-meter payload fairing |
—
|
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-meter payload fairing | Statement: [Atlas V 421, configurationFeatures, 4-meter payload fairing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationFeatures Context triple: [Atlas V 421, configurationFeatures, 4-meter payload fairing]
-
A.
configurationAvailable
Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
-
B.
featuresMode
Indicates that one entity operates in, supports, or is characterized by a particular mode or configuration specified by another entity.
-
C.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
D.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
E.
controlsFeaturesAt
Indicates that one entity has the authority or capability to manage, configure, or influence specific features at a particular location or context.
- F. None of above. chosen
Provenance (4 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_69e0b518b8948190ad69cf9a8784d397 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e75aa7b2f08190bea46f0107bcc045 |
completed | April 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.