Triple
T6903647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junkers Jumo 213 |
E159552
|
entity |
| Predicate | boostSystem |
P14379
|
FINISHED |
| Object | MW 50 water-methanol injection (on some variants) |
—
|
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: MW 50 water-methanol injection (on some variants) | Statement: [Junkers Jumo 213, boostSystem, MW 50 water-methanol injection (on some variants)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostSystem Context triple: [Junkers Jumo 213, boostSystem, MW 50 water-methanol injection (on some variants)]
-
A.
boosterType
chosen
Indicates the specific kind or category of booster associated with an entity or action.
-
B.
poweredVersionOf
Indicates that one entity is a more powerful, enhanced, or upgraded version of another entity.
-
C.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
-
D.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
E.
buildingSystem
Indicates that one entity functions as a system, subsystem, or organized set of components that serves or supports the operation of a building.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d988a5b48190a9238047e86f314c |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.