Triple
T36490251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformer architecture |
E899032
|
entity |
| Predicate | standardTransformerComplexity |
P28756
|
FINISHED |
| Object | O(L^2) |
—
|
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(L^2) | Statement: [Reformer architecture, standardTransformerComplexity, O(L^2)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTransformerComplexity Context triple: [Reformer architecture, standardTransformerComplexity, O(L^2)]
-
A.
typicalComplexity
Indicates the usual or characteristic level of complexity associated with an entity, process, or situation.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
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.
-
D.
complexityStatus
Indicates the current level or state of complexity associated with an entity or process.
-
E.
hasComplexityNote
Indicates that there is an associated explanatory note or annotation describing the complexity or intricacy of something.
- 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 3, 2026, 4:10 p.m.