Triple
T5264287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirPods Max |
E118901
|
entity |
| Predicate | includesAccessory |
P16605
|
FINISHED |
| Object | Smart Case |
—
|
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: Smart Case | Statement: [AirPods Max, includesAccessory, Smart Case]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAccessory Context triple: [AirPods Max, includesAccessory, Smart Case]
-
A.
accessory
Indicates that one entity serves as a supplementary or supporting item to another, often enhancing its function, use, or appearance.
-
B.
hasAccessoryEcosystem
Indicates that an entity is associated with a surrounding set of compatible accessories, add-ons, or peripheral products designed to work with it.
-
C.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
D.
includedWith
chosen
Indicates that one entity is provided or packaged together as part of another entity.
-
E.
hardwareIncluded
Indicates that certain hardware components are provided or come bundled together with another item or product.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd4a9888190a79ef8e64c764f86 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.