Triple
T11334455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Macintosh 9600 |
E268432
|
entity |
| Predicate | supportsDualProcessor |
P43461
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Power Macintosh 9600, supportsDualProcessor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDualProcessor Context triple: [Power Macintosh 9600, supportsDualProcessor, yes]
-
A.
supportsDualProcessors
chosen
Indicates that an entity is capable of operating with or accommodating two processors simultaneously.
-
B.
supportsIntelHyperThreading
Indicates that one entity provides compatibility with or functionality for Intel Hyper-Threading technology in relation to another entity.
-
C.
supportsSymmetricMultiprocessing
Indicates that an entity provides or is compatible with symmetric multiprocessing, allowing multiple processors to share memory and workload equally.
-
D.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
-
E.
supportsHyperThreading
Indicates that one entity provides or enables Hyper-Threading capability for another entity.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9fe5d5881908d786b212a554d8b |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787afe5a48190b8af1a3e19529641 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:33 p.m.