Triple
T29526375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NewtonThree |
E749079
|
entity |
| Predicate | thrustCycle |
P14983
|
FINISHED |
| Object | gas-generator cycle |
—
|
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: gas-generator cycle | Statement: [NewtonThree, thrustCycle, gas-generator cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustCycle Context triple: [NewtonThree, thrustCycle, gas-generator cycle]
-
A.
thrustPhase
Indicates a phase in which a propulsion system is actively producing thrust as part of a larger operation or trajectory.
-
B.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
C.
thrustControl
Indicates a relationship where one entity regulates or adjusts the thrust output or propulsion force of another entity.
-
D.
thrustCapability
Indicates the level or capacity of force an entity can exert to propel or push something, typically in a specified direction or context.
-
E.
propulsionCycle
chosen
Indicates the type or pattern of propulsion operation or cycle that characterizes how a system generates and sustains thrust or movement.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9d5df48190ad10afb467a9c7a6 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:46 p.m.