Triple
T11692983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raptor engine |
E277914
|
entity |
| Predicate | fuelChoiceRationale |
P101297
|
FINISHED |
| Object | supports in-situ resource utilization on Mars |
—
|
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: supports in-situ resource utilization on Mars | Statement: [Raptor engine, fuelChoiceRationale, supports in-situ resource utilization on Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelChoiceRationale Context triple: [Raptor engine, fuelChoiceRationale, supports in-situ resource utilization on Mars]
-
A.
fuelRole
Indicates that one entity serves as the fuel or energy source used or consumed by another entity in a process or operation.
-
B.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
-
C.
laterFuelType
Indicates that one fuel type is used or adopted after another fuel type in time.
-
D.
fuelEffect
Indicates the influence or impact that a given fuel has on a process, system, or outcome.
-
E.
fuelEfficiency
Indicates how effectively an entity uses fuel to perform a given amount of work or travel a certain distance.
- 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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a47b9eb48190976a35e91e25b56b |
completed | April 10, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69d88a7b30948190b616a9db5c5488d5 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d89546a8688190b51455b5e12caf91 |
completed | April 10, 2026, 6:14 a.m. |
Created at: April 8, 2026, 9:40 p.m.