Triple
T1870074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commodore Amiga 500 |
E39012
|
entity |
| Predicate | supportsExternalDrive |
P33362
|
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: [Commodore Amiga 500, supportsExternalDrive, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsExternalDrive Context triple: [Commodore Amiga 500, supportsExternalDrive, yes]
-
A.
supportsThirdPartyApplications
Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
-
B.
supportsExternalDisplay
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
C.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
D.
supportsInstallationMedia
Indicates that one entity is capable of accepting, handling, or working with a specified type of installation media for setup or deployment purposes.
-
E.
supportsThunderbolt
Indicates that one entity provides compatibility with or the capability to use Thunderbolt technology for another entity.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb0f630e881908cd9491aeaeb4aed |
completed | March 7, 2026, 5 a.m. |
Created at: March 4, 2026, 7:34 p.m.