Triple
T36487145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta 3910 |
E898962
|
entity |
| Predicate | strapOnBoostersType |
P14379
|
FINISHED |
| Object | Castor solid rocket motor |
—
|
NE NERFINISHED |
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: Castor solid rocket motor | Statement: [Delta 3910, strapOnBoostersType, Castor solid rocket motor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strapOnBoostersType Context triple: [Delta 3910, strapOnBoostersType, Castor solid rocket motor]
-
A.
boosterType
chosen
Indicates the specific kind or category of booster associated with an entity or action.
-
B.
usedWithBoosters
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
-
C.
boosterName
Indicates the name or designation assigned to a booster component associated with an entity or event.
-
D.
allowsBoosters
Indicates that one entity permits the use, presence, or activation of boosters in relation to another entity or context.
-
E.
boosterRecommendation
Indicates that one entity advises or prescribes a booster (e.g., an additional dose or reinforcement) for 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.