Triple
T25641820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BE-3 engine |
E642855
|
entity |
| Predicate | throttleability |
P60222
|
FINISHED |
| Object | deeply throttleable |
—
|
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: deeply throttleable | Statement: [BE-3 engine, throttleability, deeply throttleable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: throttleability Context triple: [BE-3 engine, throttleability, deeply throttleable]
-
A.
throttleable
chosen
Indicates that an action, process, or resource can have its rate or intensity adjusted, typically to limit or control its usage over time.
-
B.
tractionControl
Indicates that a system regulates wheel slip to maintain optimal traction between a vehicle’s tires and the driving surface.
-
C.
thrust
Indicates a forceful forward push or drive exerted by one entity onto another or into a particular direction.
-
D.
rateLimitingEnzyme
Indicates that the subject functions as the key regulatory enzyme that controls the overall rate of a specific metabolic pathway.
-
E.
tractionPower
Indicates the amount of mechanical or electrical power available or used to provide tractive force for movement or propulsion.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa11fa88190a7bb53c814995268 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:44 p.m.