Triple
T31776319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasProgrammingComplexity |
P28756
|
FINISHED |
| Object | lower than MLC |
—
|
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: lower than MLC | Statement: [SLC (single-level cell), hasProgrammingComplexity, lower than MLC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingComplexity Context triple: [SLC (single-level cell), hasProgrammingComplexity, lower than MLC]
-
A.
hasProgrammingScope
Indicates that something (such as a role, task, or activity) involves or includes programming-related responsibilities or subject matter.
-
B.
hasComplexity
chosen
Indicates that something possesses a certain level or type of complexity, often in terms of structure, behavior, or difficulty.
-
C.
hasProgrammingDomain
Indicates that an entity is associated with or specializes in a particular programming domain or area of software development.
-
D.
hasProgrammingFocus
Indicates that something is centered on, specialized in, or primarily concerned with programming.
-
E.
hasReasoningComplexity
Indicates that an action, process, or decision involves a certain level or type of cognitive or logical complexity in its reasoning.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a00868083b081909afc3d8d4ad56b43 |
completed | May 10, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_6a0084f5f72c8190b08afa82690e322a |
completed | May 10, 2026, 1:15 p.m. |
Created at: April 30, 2026, 11:35 p.m.