Triple
T30300176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dictionary (Swift) |
E770631
|
entity |
| Predicate | accessComplexity |
P28756
|
FINISHED |
| Object | average O(1) lookup by key |
—
|
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: average O(1) lookup by key | Statement: [Dictionary (Swift), accessComplexity, average O(1) lookup by key]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessComplexity Context triple: [Dictionary (Swift), accessComplexity, average O(1) lookup by key]
-
A.
attackComplexity
Indicates the level of difficulty or effort required by an attacker to successfully exploit a vulnerability or carry out an attack.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
controlsComplexityBy
Indicates that one entity manages, limits, or regulates the complexity of another entity, process, or system.
-
D.
accessComparedTo
Indicates how the level, ease, or quality of access to something compares between two entities or contexts.
-
E.
accessScope
Indicates the extent or boundaries of access that one entity has to another entity or resource.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 7:48 p.m.