Triple
T12999063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Aces |
E322117
|
entity |
| Predicate | accelerationMechanism |
P63810
|
FINISHED |
| Object | cable lift acceleration |
—
|
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: cable lift acceleration | Statement: [Flying Aces, accelerationMechanism, cable lift acceleration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accelerationMechanism Context triple: [Flying Aces, accelerationMechanism, cable lift acceleration]
-
A.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
B.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
C.
amplificationMechanism
Indicates the process or mechanism by which a signal, effect, or influence is increased in strength, magnitude, or impact.
-
D.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
E.
launchMechanism
chosen
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7b268c8190b8bb855e9de23c3b |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:46 p.m.