Triple
T26966624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EXPTIME |
E679188
|
entity |
| Predicate | typicalRunningTimeForm |
P199243
|
FINISHED |
| Object | 2^{n^k} for some constant k |
—
|
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: 2^{n^k} for some constant k | Statement: [EXPTIME, typicalRunningTimeForm, 2^{n^k} for some constant k]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRunningTimeForm
Context triple: [EXPTIME, typicalRunningTimeForm, 2^{n^k} for some constant k]
-
A.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
B.
typicalRuntimePerShort
Indicates the usual or average amount of time it takes to complete a short instance of the referenced activity or process.
-
C.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
D.
hasRunningTimeCategory
Indicates that an entity is associated with a specific category based on its running time or duration.
-
E.
runtimeMinutes
Indicates the total duration of something, typically a media work or process, measured in minutes.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
| PDg | Predicate description generation | batch_69ff28948b34819090e7e8b0b19535b2 |
completed | May 9, 2026, 12:29 p.m. |
Created at: April 27, 2026, 6:36 a.m.