Triple
T31776279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasReliability |
P95504
|
FINISHED |
| Object | high reliability |
—
|
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: high reliability | Statement: [SLC (single-level cell), hasReliability, high reliability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReliability Context triple: [SLC (single-level cell), hasReliability, high reliability]
-
A.
hasReliabilityGoal
Indicates that an entity is associated with or assigned a specific reliability-related objective or target.
-
B.
reliabilityHigherThan
Indicates that one entity is considered to have greater reliability than another entity.
-
C.
reliabilityCharacteristic
chosen
Indicates that one entity specifies or embodies a reliability-related property, feature, or performance attribute of another entity.
-
D.
hasHistoricalReliability
Indicates that something is supported by credible historical evidence and is considered trustworthy as an account of past events.
-
E.
reliabilityRecord
Indicates that there exists a record or documentation capturing the reliability characteristics, performance, or history associated with an entity or relationship.
- 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_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: April 30, 2026, 11:35 p.m.