Triple

T31776288
Position Surface form Disambiguated ID Type / Status
Subject SLC (single-level cell) E811072 entity
Predicate hasEnduranceAdvantageOver P187583 FINISHED
Object MLC (multi-level cell) 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: MLC (multi-level cell) | Statement: [SLC (single-level cell), hasEnduranceAdvantageOver, MLC (multi-level cell)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEnduranceAdvantageOver
Context triple: [SLC (single-level cell), hasEnduranceAdvantageOver, MLC (multi-level cell)]
  • A. hasSurvivalSkill
    Indicates that an entity possesses the ability or knowledge necessary to endure and function effectively in challenging or threatening conditions.
  • B. cannotBeDefeatedBy
    Indicates that one entity is invulnerable to defeat by another specified entity or set of entities.
  • C. hasBaseDefense
    Indicates that an entity possesses a specified level or value of defensive capability in its default or starting state.
  • D. survivesAttackBy
    Indicates that one entity remains alive, intact, or functional after being subjected to an attack initiated by another entity.
  • E. hasDefenderStrength
    Indicates that an entity possesses a certain level or measure of defensive capability or protective power.
  • F. None of above. chosen

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_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
PDg Predicate description generation batch_69fb6fdab95c81909acff3c6a2359787 completed May 6, 2026, 4:44 p.m.
Created at: April 30, 2026, 11:35 p.m.