Triple
T35076583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mi Band fitness trackers |
E1012323
|
entity |
| Predicate | pairedWithApp |
P181758
|
FINISHED |
| Object | Mi Fit app |
—
|
NE NERFINISHED |
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: Mi Fit app | Statement: [Mi Band fitness trackers, pairedWithApp, Mi Fit app]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pairedWithApp Context triple: [Mi Band fitness trackers, pairedWithApp, Mi Fit app]
-
A.
companionApp
chosen
Indicates that one entity functions as a companion application that complements, extends, or supports the use of another entity.
-
B.
pairedWithFunctionally
Indicates that one entity is functionally matched or coupled with another to perform a complementary or corresponding role.
-
C.
pairedWithName
Indicates that one entity is associated or matched with another entity identified by a specific name.
-
D.
isCompanionAppFor
Indicates that one application is designed to complement, extend, or interact with another primary application as its companion.
-
E.
associatedWithDuo
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865b4684819093f95e659522b75e |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.