Triple
T26966679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | complexityMeasure |
P27167
|
FINISHED |
| Object | randomized time complexity |
—
|
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: randomized time complexity | Statement: [BPP, complexityMeasure, randomized time complexity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complexityMeasure Context triple: [BPP, complexityMeasure, randomized time complexity]
-
A.
assumesComplexityMeasure
Indicates that one entity adopts or takes for granted a particular method or standard for measuring complexity in relation to another entity or context.
-
B.
parameterizedComplexity
Indicates that the relationship or action is analyzed or characterized in terms of its computational complexity as a function of one or more explicit parameters.
-
C.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
D.
complexityStatus
Indicates the current level or state of complexity associated with an entity or process.
-
E.
timeComplexity
chosen
Indicates the computational growth rate of an algorithm’s resource usage (typically time) as a function of input size.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 6:36 a.m.