Triple
T21849218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PW2040 |
E539457
|
entity |
| Predicate | thrustVector |
P145557
|
FINISHED |
| Object | fixed |
—
|
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: fixed | Statement: [PW2040, thrustVector, fixed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrustVector Context triple: [PW2040, thrustVector, fixed]
-
A.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
B.
thrustDistribution
Indicates how thrust or propulsive force is apportioned or spread among different components, directions, or stages within a system.
-
C.
thrustVectorControl
Indicates the capability to direct or adjust the direction of thrust from a propulsion system to control an object's attitude or trajectory.
-
D.
thrustClass
Indicates the classification of an engine or propulsion system based on the amount or category of thrust it can produce.
-
E.
thrustControl
Indicates a relationship where one entity regulates or adjusts the thrust output or propulsion force of another entity.
- 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_69e0c476c3c88190a92d08ebb59a128a |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0bd56f4e081909a906b64c1019e6a |
completed | April 28, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 6:55 p.m.