Triple
T14372627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misfit Link |
E356392
|
entity |
| Predicate | hasNotificationType |
P8650
|
FINISHED |
| Object | LED indicator |
—
|
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: LED indicator | Statement: [Misfit Link, hasNotificationType, LED indicator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotificationType Context triple: [Misfit Link, hasNotificationType, LED indicator]
-
A.
hasCommunicationType
Indicates that one entity uses, supports, or is associated with a particular form or mode of communication.
-
B.
hasFeedbackType
chosen
Indicates that an entity is associated with a specific category or type of feedback it provides or receives.
-
C.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
D.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
E.
hasTriggerType
Indicates that an event, condition, or mechanism is associated with a specific type or category of trigger that initiates it.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fb2082c8190b42cc5f2bab4f574 |
completed | April 14, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a9cb3e081909f6b33fdd939bb9e |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:15 a.m.