Triple
T19508544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirPods Pro charging case (1st generation) |
E488088
|
entity |
| Predicate | supportsPairing |
P108812
|
FINISHED |
| Object | via case button and nearby Apple device |
—
|
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: via case button and nearby Apple device | Statement: [AirPods Pro charging case (1st generation), supportsPairing, via case button and nearby Apple device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPairing Context triple: [AirPods Pro charging case (1st generation), supportsPairing, via case button and nearby Apple device]
-
A.
supportsStereoPairing
Indicates that an entity is capable of being paired with another similar entity to function together as a synchronized stereo audio system.
-
B.
hasPairingScheme
chosen
Indicates that there is an associated method or scheme by which two or more items are systematically paired or matched with each other.
-
C.
canPairRegistersFor
Indicates that two registers are compatible and allowed to be paired together for a combined or coordinated operation.
-
D.
supportsBridging
Indicates that one entity enables or facilitates a bridging connection or transition between two otherwise separate entities, systems, or contexts.
-
E.
featuresOnscreenPairing
Indicates that two entities appear together as an on-screen pairing within the same visual or filmed context.
- 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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6351426448190aec1ee26c09faa24 |
completed | April 20, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7bd25881908caa04eaef1f6718 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.