Triple
T1082796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polynomial Root Finder |
E23983
|
entity |
| Predicate | performance |
P23737
|
FINISHED |
| Object | computes roots quickly |
—
|
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: computes roots quickly | Statement: [Polynomial Root Finder, performance, computes roots quickly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performance Context triple: [Polynomial Root Finder, performance, computes roots quickly]
-
A.
impactOnPerformance
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
-
B.
featuresPerformanceBy
Indicates a relationship where something (such as an event, work, or production) includes or showcases a performance given by a particular performer or group.
-
C.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
D.
performanceCores
Indicates a relationship where certain cores within a processor are designated as high-performance cores optimized for speed and intensive tasks.
-
E.
precision
Indicates the degree to which an action, measurement, or outcome is carried out with exactness, minimal deviation, and fine-grained accuracy.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95e56948190a1e92367ad7240b7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73f4310819086281f8ec67d1a32 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.