Triple
T29998571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RD-171 |
E762097
|
entity |
| Predicate | usesCommonTurbopump |
P184603
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [RD-171, usesCommonTurbopump, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommonTurbopump Context triple: [RD-171, usesCommonTurbopump, true]
-
A.
usesTurbopumps
Indicates that an entity employs turbopumps to pressurize and deliver propellants or fluids within its operation or system.
-
B.
turbopumpType
Indicates the specific kind or classification of turbopump associated with an entity.
-
C.
numberOfTurbopumps
Indicates the quantity of turbopumps associated with or used by a given entity or system.
-
D.
pumps
Indicates that one entity moves or circulates a substance (such as a fluid or gas) into, out of, or through another entity using pressure or mechanical action.
-
E.
hasVacuumSystem
Indicates that one entity is equipped with, or includes as a component, a vacuum system.
- F. None of above. chosen
Provenance (4 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 29, 2026, 6:40 p.m.