Triple
T8611441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | eMMC |
E203921
|
entity |
| Predicate | performanceComparedToUFS |
P83874
|
FINISHED |
| Object | lower |
—
|
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 | Statement: [eMMC, performanceComparedToUFS, lower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceComparedToUFS Context triple: [eMMC, performanceComparedToUFS, lower]
-
A.
advantageOverSATA
Indicates that one entity has a performance or functional benefit when compared to SATA.
-
B.
disadvantageComparedToSATA
Indicates that something has a drawback, limitation, or weaker performance when compared to SATA.
-
C.
featureLevelComparedTo
Indicates a comparative relationship between entities based on their feature level, specifying how one entity’s feature level ranks relative to another’s.
-
D.
typicalEfficiencyComparedToPredecessor
Indicates how the usual or average efficiency of something compares to that of its predecessor.
-
E.
yieldPotentialComparedToTraditionalVarieties
Indicates how the expected crop yield associated with something compares in magnitude to the yield of conventional or traditional varieties.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46fc31e08190aab5ab8f92f3315c |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:25 p.m.