Triple
T37301357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athena II |
E925951
|
entity |
| Predicate | stage1Engine |
P7194
|
FINISHED |
| Object | Castor 120 |
—
|
NE NERFINISHED |
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: Castor 120 | Statement: [Athena II, stage1Engine, Castor 120]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stage1Engine Context triple: [Athena II, stage1Engine, Castor 120]
-
A.
firstStageEngine
chosen
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
-
B.
firstStageEngineOrigin
Indicates the place or source from which the first-stage engine of a launch vehicle or rocket originates or is produced.
-
C.
firstStageEngineCycle
Indicates that one engine cycle is used as the primary or initial propulsion stage in a multi-stage launch or propulsion system.
-
D.
firstStageEngineVariant
Indicates that one engine is a specific variant or version of the engine used in the first stage of a launch vehicle or rocket system.
-
E.
firstStageEngineSupplier
Indicates that one entity serves as the supplier of the first-stage engine for another entity, typically a launch vehicle or rocket.
- 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_69f76eb1bc508190924e9fa5d8acdeb3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.