Triple
T30386547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDE Connect |
E772967
|
entity |
| Predicate | androidAppStore |
P14571
|
FINISHED |
| Object | Google Play Store |
E13751
|
NE 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: Google Play Store | Statement: [KDE Connect, androidAppStore, Google Play Store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: androidAppStore Context triple: [KDE Connect, androidAppStore, Google Play Store]
-
A.
supportsGooglePlay
Indicates that an entity is compatible with and can run or provide access to Google Play services or applications.
-
B.
hasAndroidPartner
Indicates that an entity has another entity as its romantic or life partner who is an android.
-
C.
applicationTool
Indicates that one entity is a tool or instrument used to apply, operate, or carry out the function of another entity.
-
D.
hasApp
chosen
Indicates that an entity possesses, provides, or is associated with a particular application.
-
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 (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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68597e99881908132be20fff643f5 |
completed | May 2, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a27894c378c8190a5e3b1fd63351626 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.