Triple
T34540364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Python 3.11 |
E886788
|
entity |
| Predicate | maxSpeedupReported |
P55146
|
FINISHED |
| Object | up to 1.6x |
—
|
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: up to 1.6x | Statement: [Python 3.11, maxSpeedupReported, up to 1.6x]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxSpeedupReported Context triple: [Python 3.11, maxSpeedupReported, up to 1.6x]
-
A.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
-
B.
typicalSpeedup
chosen
Indicates the usual or expected performance improvement (e.g., reduction in time or increase in speed) achieved when applying one method, system, or configuration relative to another.
-
C.
maximumCurrentSpeed
Indicates the highest current speed value that an entity is allowed or able to reach under present conditions.
-
D.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
E.
maximumOperatingMach
Indicates the highest machine operating level, capacity, or intensity at which the related entity is allowed or designed to function.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff3ae60819089447abe3ff9e784 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.