Triple
T38052525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh 5400 series |
E949804
|
entity |
| Predicate | typicalRamType |
P9896
|
FINISHED |
| Object | 72-pin EDO DIMM |
—
|
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: 72-pin EDO DIMM | Statement: [Power Macintosh 5400 series, typicalRamType, 72-pin EDO DIMM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRamType Context triple: [Power Macintosh 5400 series, typicalRamType, 72-pin EDO DIMM]
-
A.
typicalRAMRange
Indicates the usual or commonly expected range of RAM capacity associated with an entity.
-
B.
typicalRAMRangeMB
Indicates the usual or expected range of RAM capacity, measured in megabytes, associated with an entity.
-
C.
typicalRAMExpansionSizes
Indicates the commonly used or standard memory capacity increments by which a system’s RAM can be expanded.
-
D.
hasRAM
Indicates that an entity possesses or is equipped with a specified amount or type of random-access memory (RAM).
-
E.
memoryType
chosen
Indicates the specific category or kind of memory associated with an entity or process.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.