Triple
T30384043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-C200 |
E772900
|
entity |
| Predicate | earbudFeature |
P48651
|
FINISHED |
| Object | magnetic earbuds |
—
|
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: magnetic earbuds | Statement: [Sony WI-C200, earbudFeature, magnetic earbuds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earbudFeature Context triple: [Sony WI-C200, earbudFeature, magnetic earbuds]
-
A.
supportsBluetoothCodec
Indicates that one entity is capable of using or is compatible with a specified Bluetooth audio codec in its operation or communication.
-
B.
hasAudioFeature
chosen
Indicates that one entity possesses or is associated with a specific audio-related characteristic or property.
-
C.
supportsLightningEarPods
Indicates that one entity is compatible with and can be used with Lightning-connector EarPods.
-
D.
supports3_5mmJack
Indicates that one entity is compatible with or provides a 3.5mm audio jack connection for another entity.
-
E.
earDescription
Indicates a textual description of the characteristics or appearance of an entity’s ear or ears.
- 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_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_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.