Triple
T2874385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Mac G5 |
E56840
|
entity |
| Predicate | supportsDualProcessors |
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 Mac G5, supportsDualProcessors, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDualProcessors Context triple: [Power Mac G5, supportsDualProcessors, yes]
-
A.
multitaskingSupport
Indicates that an entity is capable of performing multiple tasks or operations concurrently or in parallel.
-
B.
supportsMultitaskingOfDOSPrograms
Indicates that a system or environment is capable of running and managing multiple DOS programs simultaneously.
-
C.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
D.
secondaryCpu
Indicates that one CPU functions as a secondary or backup processor in relation to a primary CPU.
-
E.
supportsMultipleBusMasters
Indicates that the system or component allows more than one bus master to control or access the bus concurrently or in turn.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0032ddc8190bb4d15ec7e3c63e8 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:03 p.m.