Triple
T31776291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasReliabilityAdvantageOver |
P163726
|
FINISHED |
| Object | MLC (multi-level cell) |
E811073
|
NE 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: MLC (multi-level cell) | Statement: [SLC (single-level cell), hasReliabilityAdvantageOver, MLC (multi-level cell)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliabilityAdvantageOver Context triple: [SLC (single-level cell), hasReliabilityAdvantageOver, MLC (multi-level cell)]
-
A.
reliabilityHigherThan
chosen
Indicates that one entity is considered to have greater reliability than another entity.
-
B.
isStrongerProtectionThan
Indicates that one form of protection provides a higher level of security, defense, or safeguarding compared to another.
-
C.
reliabilityCharacteristic
Indicates that one entity specifies or embodies a reliability-related property, feature, or performance attribute of another entity.
-
D.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
E.
unreliableAgainst
Indicates that one entity cannot be consistently depended on to perform effectively or correctly when dealing with, opposing, or interacting with another specified entity.
- F. None of above.
Provenance (4 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_6a01a23d8b148190ac2c8765aa9227c4 |
completed | May 11, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2d9d543d3881909e683468ba168186 |
completed | June 13, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a01a1e8bb90819096647e929bfb3db8 |
completed | May 11, 2026, 9:31 a.m. |
Created at: April 30, 2026, 11:35 p.m.