Triple
T25664493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-4 |
E643473
|
entity |
| Predicate | engineConfigurationOnNewGlenn |
P82736
|
FINISHED |
| Object | cluster of seven BE-4 engines |
—
|
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: cluster of seven BE-4 engines | Statement: [BE-4, engineConfigurationOnNewGlenn, cluster of seven BE-4 engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineConfigurationOnNewGlenn Context triple: [BE-4, engineConfigurationOnNewGlenn, cluster of seven BE-4 engines]
-
A.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
B.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
-
C.
engineModelOption
chosen
Indicates that a particular engine model is available as a configurable option for an item or product.
-
D.
engineClass
Indicates the classification or type category assigned to an engine within a given system or context.
-
E.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faf1f9c48190ad732234e836b143 |
completed | May 2, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7 p.m.