Triple
T30913468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Integral Active Steering |
E787517
|
entity |
| Predicate | effectAtHighSpeed |
P181254
|
FINISHED |
| Object | increases directional stability |
—
|
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: increases directional stability | Statement: [Integral Active Steering, effectAtHighSpeed, increases directional stability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectAtHighSpeed Context triple: [Integral Active Steering, effectAtHighSpeed, increases directional stability]
-
A.
effectAtLowSpeed
Indicates that the described effect or influence occurs specifically when the entity is moving or operating at a low speed.
-
B.
speed
Indicates the rate at which an entity moves or changes position over time.
-
C.
higherLevelEffect
Indicates that one entity produces an indirect or overarching influence or consequence on another entity or process at a more abstract or aggregated level.
-
D.
capturesEffectOf
Indicates that one entity represents or records the impact, consequence, or outcome produced by another entity or process.
-
E.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
- 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_69f224be300c8190a6513ce1ee0a7026 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 29, 2026, 8:51 p.m.