Triple
T34844581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Booster Core |
E1004430
|
entity |
| Predicate | configurationInDeltaIVHeavy |
P28533
|
FINISHED |
| Object | three CBCs strapped together |
—
|
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: three CBCs strapped together | Statement: [Common Booster Core, configurationInDeltaIVHeavy, three CBCs strapped together]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationInDeltaIVHeavy Context triple: [Common Booster Core, configurationInDeltaIVHeavy, three CBCs strapped together]
-
A.
testedConfiguration
Indicates that a particular configuration has been examined or validated through testing in relation to another entity or context.
-
B.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
C.
containsDelta
Indicates that one entity includes or encompasses a change, difference, or delta associated with another entity.
-
D.
configurationOptionIn
chosen
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
E.
configurationVia
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.