Triple
T23660953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan IIID |
E584442
|
entity |
| Predicate | fuelTypeSecondStage |
P8435
|
FINISHED |
| Object | Aerozine 50 |
—
|
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: Aerozine 50 | Statement: [Titan IIID, fuelTypeSecondStage, Aerozine 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fuelTypeSecondStage Context triple: [Titan IIID, fuelTypeSecondStage, Aerozine 50]
-
A.
propellantSecondStage
chosen
Indicates that an entity serves as the propellant used in the second stage of a multi-stage propulsion system.
-
B.
propellantTypeFirstSecondStages
Indicates that the first and second stages of a launch vehicle use the specified type of propellant.
-
C.
secondaryFuel
Indicates that an entity uses or is associated with a secondary (additional or backup) fuel source in addition to its primary fuel.
-
D.
fuelUpperStage
Indicates that an agent supplies or loads propellant into the upper stage of a launch vehicle or rocket.
-
E.
engineTypeSecondStage
Indicates the type or classification of the engine used in the second stage of a multi-stage system or vehicle.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3601ce481909a4ae9d633b9a343 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.