Triple
T18791114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merge sort |
E459515
|
entity |
| Predicate | spaceComplexityTypical |
P55525
|
FINISHED |
| Object | O(n) |
—
|
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(n) | Statement: [Merge sort, spaceComplexityTypical, O(n)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceComplexityTypical Context triple: [Merge sort, spaceComplexityTypical, O(n)]
-
A.
spaceComplexity
chosen
Indicates the relationship between an algorithm and the amount of memory it requires as a function of input size.
-
B.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
C.
spaceType
Indicates the category or kind of physical or conceptual space associated with an entity.
-
D.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
E.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.