Triple
T35290920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 578 |
E1019220
|
entity |
| Predicate | supportsAppleDesktopBusPeripherals |
P193521
|
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: [Macintosh Performa 578, supportsAppleDesktopBusPeripherals, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAppleDesktopBusPeripherals Context triple: [Macintosh Performa 578, supportsAppleDesktopBusPeripherals, yes]
-
A.
supportsPCConnectivity
Indicates that one entity enables or is compatible with connection or communication to a personal computer.
-
B.
supportsDockingStations
Indicates that one entity is compatible with and can function correctly when connected to docking stations associated with another entity.
-
C.
supportsThunderbolt
Indicates that one entity provides compatibility with or the capability to use Thunderbolt technology for another entity.
-
D.
supportedBusInterface
chosen
Indicates that one entity provides or is compatible with a particular bus interface used for communication or connection with other components.
-
E.
usesMAC
Indicates that one entity employs or operates another entity via its Media Access Control (MAC) address or MAC-based mechanism.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.