Triple
T31776294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLC (single-level cell) |
E811072
|
entity |
| Predicate | hasSpeedAdvantageOver |
P66402
|
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), hasSpeedAdvantageOver, MLC (multi-level cell)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeedAdvantageOver Context triple: [SLC (single-level cell), hasSpeedAdvantageOver, MLC (multi-level cell)]
-
A.
fasterThan
chosen
Indicates that one entity moves, operates, or progresses at a higher speed than another entity.
-
B.
hasEnduranceAdvantageOver
Indicates that one entity possesses greater stamina or lasting physical capability compared to another entity.
-
C.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
D.
racedWith
Indicates that one entity participated in a race or competitive speed event together with another entity.
-
E.
hasHighSpeedPotential
Indicates that an entity possesses the capability or conditions to achieve or sustain a high rate of speed, even if it is not currently doing so.
- 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_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 30, 2026, 11:35 p.m.