Triple
T4424323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaction Motors XLR11 |
E95173
|
entity |
| Predicate | fuelFeedSystem |
P39480
|
FINISHED |
| Object | pressurized tanks |
—
|
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: pressurized tanks | Statement: [Reaction Motors XLR11, fuelFeedSystem, pressurized tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelFeedSystem Context triple: [Reaction Motors XLR11, fuelFeedSystem, pressurized tanks]
-
A.
fuelSystem
Indicates a relationship where one entity serves as the fuel system (or part of it) that supplies, stores, or manages fuel for the operation of another entity.
-
B.
refuellingSystem
Indicates a system or mechanism used to supply fuel from one entity to another.
-
C.
propellantFeedSystem
chosen
Indicates a relationship where a system supplies, regulates, or transports propellant to a propulsion or engine unit.
-
D.
fuelPumpDrive
Indicates that one component provides the mechanical drive or actuation needed to operate a fuel pump.
-
E.
fuelFraction
Indicates the proportion of an object's total mass or capacity that consists of fuel.
- 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_69b3453a36908190b95a79a297ca083c |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554ca5208190ba2661616dcf071c |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.