Triple
T2546092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Draco thrusters |
E57904
|
entity |
| Predicate | controlAxis |
P32356
|
FINISHED |
| Object | roll |
—
|
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: roll | Statement: [Draco thrusters, controlAxis, roll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlAxis Context triple: [Draco thrusters, controlAxis, roll]
-
A.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
B.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
C.
usesAxis
chosen
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
-
D.
controlLayout
Indicates that one entity determines or manages the spatial or structural arrangement of another entity.
-
E.
controlSurfaces
Indicates that one entity functions as a control surface or set of control surfaces used to influence, steer, or regulate the behavior or state of another entity.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2e5152c8190b31a5e732d0dde44 |
completed | March 7, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.