Triple
T6366384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitbit Ionic |
E143238
|
entity |
| Predicate | hasStrapType |
P70222
|
FINISHED |
| Object | interchangeable bands |
—
|
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: interchangeable bands | Statement: [Fitbit Ionic, hasStrapType, interchangeable bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStrapType Context triple: [Fitbit Ionic, hasStrapType, interchangeable bands]
-
A.
soleType
Indicates the specific kind or design category of a sole associated with an item (such as footwear or a similar object).
-
B.
hasStratotype
Indicates that one entity serves as the designated standard or reference example (stratotype) for defining the stratigraphic characteristics of another entity.
-
C.
wearerType
Indicates the type or category of entity that is intended to wear or use the associated item.
-
D.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
E.
hasGripType
Indicates that one entity possesses or uses a specific type or style of grip in relation to another entity or action.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06811de2881909ead116117956981 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:32 p.m.