Triple
T30384002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-V6 |
E772899
|
entity |
| Predicate | cableSide |
P169746
|
FINISHED |
| Object | single-sided cable |
—
|
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: single-sided cable | Statement: [Sony MDR-V6, cableSide, single-sided cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cableSide Context triple: [Sony MDR-V6, cableSide, single-sided cable]
-
A.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
B.
cableEnd
Indicates that one entity represents an endpoint or terminal position of a cable in relation to another entity.
-
C.
cableDetachable
Indicates that the cable associated with an object can be removed or disconnected from it.
-
D.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
E.
hasNumberOfCables
Indicates the relationship that specifies how many cables are associated with a given 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6851d7b288190a4d1d974e1f3ea16 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:01 p.m.