Triple
T30350638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony MDR-7506 |
E771979
|
entity |
| Predicate | earCoupling |
P44898
|
FINISHED |
| Object | circumaural |
—
|
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: circumaural | Statement: [Sony MDR-7506, earCoupling, circumaural]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earCoupling Context triple: [Sony MDR-7506, earCoupling, circumaural]
-
A.
earType
chosen
Indicates the specific kind or classification of ears associated with an entity.
-
B.
earDescription
Indicates a textual description of the characteristics or appearance of an entity’s ear or ears.
-
C.
earFunction
Indicates that an entity’s ear is used for a particular function or role, such as hearing, balance, or sound localization, in relation to another entity or context.
-
D.
earTipMaterial
Indicates the material from which the tip of an ear (or ear-like component) is made.
-
E.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
- 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_69f6820b4b8c81908f5bbae956565ec0 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.