Triple
T1180395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fitbit OS |
E25121
|
entity |
| Predicate | firstReleaseApproximate |
P18472
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Fitbit OS, firstReleaseApproximate, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstReleaseApproximate Context triple: [Fitbit OS, firstReleaseApproximate, 2017]
-
A.
firstReleaseVersion
Indicates the specific version identifier associated with the initial public release of something.
-
B.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
C.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
D.
firstGenerationReleaseDate
Indicates the calendar date on which the first generation or initial version of something was officially released.
-
E.
firstAppearedAt
chosen
Indicates the point in time or specific event at which an entity was first introduced, observed, or became known.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd32c5f48190b4e2d39fa052cbb7 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb59ca6c81908597a81646674aaa |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.