Triple
T30428493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-1AM2 |
E774096
|
entity |
| Predicate | hasBalancedCableOption |
P182767
|
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: [Sony MDR-1AM2, hasBalancedCableOption, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBalancedCableOption Context triple: [Sony MDR-1AM2, hasBalancedCableOption, yes]
-
A.
hasNumberOfCables
Indicates the relationship that specifies how many cables are associated with a given entity.
-
B.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
C.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
D.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
E.
hasNumberOfMainCables
Indicates the quantity of primary cables associated with or used by an 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78fd3fd888190b7db0b563f298585 |
completed | May 3, 2026, 6:11 p.m. |
Created at: April 29, 2026, 8:06 p.m.