Triple
T18337336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electric Now |
E439305
|
entity |
| Predicate | hasAppPlatform |
P43193
|
FINISHED |
| Object | mobile devices |
—
|
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: mobile devices | Statement: [Electric Now, hasAppPlatform, mobile devices]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAppPlatform Context triple: [Electric Now, hasAppPlatform, mobile devices]
-
A.
hasPlatformType
Indicates that an entity is associated with or characterized by a specific type or category of platform.
-
B.
hasApp
Indicates that an entity possesses, provides, or is associated with a particular application.
-
C.
hasPrimaryPlatform
Indicates that one entity is designated as the main or principal platform associated with another entity.
-
D.
hasTargetPlatform
chosen
Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
-
E.
hasAndroid
Indicates that an entity possesses, is equipped with, or is associated with an Android device, system, or component.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ece387881909a5da0aa4370489c |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.