Triple
T14773321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyer–Moore string-search algorithm |
E347189
|
entity |
| Predicate | hasSpaceComplexity |
P55525
|
FINISHED |
| Object | O(σ + m) |
—
|
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: O(σ + m) | Statement: [Boyer–Moore string-search algorithm, hasSpaceComplexity, O(σ + m)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpaceComplexity Context triple: [Boyer–Moore string-search algorithm, hasSpaceComplexity, O(σ + m)]
-
A.
spaceComplexity
chosen
Indicates the relationship between an algorithm and the amount of memory it requires as a function of input size.
-
B.
hasComplexity
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
hasComplex
Indicates that one entity possesses, is associated with, or is part of a larger composite structure or complex formed with another entity.
-
D.
hasSpaceType
Indicates that one entity is associated with, or classified by, a particular type or category of space.
-
E.
hasCentralSpace
Indicates that an entity includes or is characterized by a primary, central area or space within its overall structure.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81485e08190be35baafcf22b6f2 |
completed | April 14, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69de8c02e5c08190943c27594026faf7 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.