Triple
T22134350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-4 |
E546986
|
entity |
| Predicate | primaryMaterialUseCase |
P131315
|
FINISHED |
| Object | heavy-lift launch vehicles |
—
|
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: heavy-lift launch vehicles | Statement: [BE-4, primaryMaterialUseCase, heavy-lift launch vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMaterialUseCase Context triple: [BE-4, primaryMaterialUseCase, heavy-lift launch vehicles]
-
A.
primaryMaterialOnDisplay
Indicates that a material is the main or dominant substance featured in the visible presentation or display of an object or item.
-
B.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
-
C.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
D.
primaryUseOf
chosen
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
E.
originalPrimaryUse
Indicates that something was first or chiefly intended to be used for a particular purpose or function.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129b8f4248190b6342c8d00942c25 |
completed | April 28, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.