Triple
T34101079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Card, Moran, and Newell keystroke-level model |
E874569
|
entity |
| Predicate | timeEstimationMethod |
P21771
|
FINISHED |
| Object | sum of operator times |
—
|
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: sum of operator times | Statement: [Card, Moran, and Newell keystroke-level model, timeEstimationMethod, sum of operator times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeEstimationMethod Context triple: [Card, Moran, and Newell keystroke-level model, timeEstimationMethod, sum of operator times]
-
A.
approximateEstimation
Indicates an estimation relationship where one value or assessment is only roughly or closely, but not exactly, equal to another.
-
B.
timingMethod
chosen
Indicates the method or technique used to measure or record the timing of an event or process.
-
C.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
D.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
E.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c692af8819084489cd50607ca1b |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:53 a.m.