Triple
T35594230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh Performa 5300 series |
E1028582
|
entity |
| Predicate | hasDriveBay |
P143299
|
FINISHED |
| Object | 3.5-inch floppy disk drive |
—
|
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: 3.5-inch floppy disk drive | Statement: [Macintosh Performa 5300 series, hasDriveBay, 3.5-inch floppy disk drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDriveBay Context triple: [Macintosh Performa 5300 series, hasDriveBay, 3.5-inch floppy disk drive]
-
A.
hasBays
chosen
Indicates that something possesses or contains one or more bays, such as recessed areas, compartments, or harbor inlets.
-
B.
hasVehicleFeature
Indicates that a vehicle possesses, includes, or is equipped with a specific feature or characteristic.
-
C.
hasFrunk
Indicates that an entity possesses a front trunk or front storage compartment.
-
D.
hasBusBays
Indicates that a location or facility is equipped with one or more designated bus bays for buses to stop, load, or unload passengers.
-
E.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.