Triple
T27762493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transformer-XL |
E701503
|
entity |
| Predicate | evaluationSpeedupReason |
P74576
|
FINISHED |
| Object | reuse of cached hidden states |
—
|
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: reuse of cached hidden states | Statement: [Transformer-XL, evaluationSpeedupReason, reuse of cached hidden states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evaluationSpeedupReason Context triple: [Transformer-XL, evaluationSpeedupReason, reuse of cached hidden states]
-
A.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
B.
typicalSpeedup
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.
performanceImprovementReason
chosen
Indicates the reason or cause behind an observed or intended improvement in performance.
-
D.
decisionSpeed
Indicates how quickly a decision is reached or made in a given context.
-
E.
compilationSpeed
Indicates how quickly a program or source code is processed and transformed into executable form by a compiler.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63766dcc48190a916106fbf8ad619 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:28 p.m.