Triple
T28685984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long March 2E |
E729133
|
entity |
| Predicate | hasBooster |
P14379
|
FINISHED |
| Object | strap-on liquid rocket boosters |
—
|
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: strap-on liquid rocket boosters | Statement: [Long March 2E, hasBooster, strap-on liquid rocket boosters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBooster Context triple: [Long March 2E, hasBooster, strap-on liquid rocket boosters]
-
A.
usedWithBoosters
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
-
B.
boosterType
chosen
Indicates the specific kind or category of booster associated with an entity or action.
-
C.
boosterName
Indicates the name or designation assigned to a booster component associated with an entity or event.
-
D.
hasBoostMechanic
Indicates that one entity (typically a game or system) includes a mechanic that temporarily increases the power, speed, or effectiveness of another entity.
-
E.
allowsBoosters
Indicates that one entity permits the use, presence, or activation of boosters in relation to another entity or context.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 28, 2026, 5:32 a.m.