Triple
T30350643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-7506 |
E771979
|
entity |
| Predicate | adapterIncluded |
P33720
|
FINISHED |
| Object | 6.3 mm stereo adapter |
—
|
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: 6.3 mm stereo adapter | Statement: [Sony MDR-7506, adapterIncluded, 6.3 mm stereo adapter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adapterIncluded Context triple: [Sony MDR-7506, adapterIncluded, 6.3 mm stereo adapter]
-
A.
hardwareIncluded
chosen
Indicates that certain hardware components are provided or come bundled together with another item or product.
-
B.
hasHardwareCompatibilityWith
Indicates that two hardware components or systems can operate together correctly and reliably without conflicts or incompatibilities.
-
C.
componentIncluded
Indicates that one entity is a constituent part or subcomponent that is contained within or included in another entity.
-
D.
platformIncludes
Indicates that a platform contains, supports, or provides access to the specified component, feature, or content.
-
E.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 7:56 p.m.