Triple
T30387229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDE Women |
E772981
|
entity |
| Predicate | softwareContext |
P169144
|
FINISHED |
| Object | KDE software |
—
|
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: KDE software | Statement: [KDE Women, softwareContext, KDE software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareContext Context triple: [KDE Women, softwareContext, KDE software]
-
A.
softwareSystem
Indicates a relationship where an entity functions as, or is classified as, a software system.
-
B.
softwareFormat
Indicates that one entity specifies or uses the file or data format in which a software-related item is encoded, stored, or delivered.
-
C.
softwareLibrary
Indicates that one entity is a software library that provides code, functionality, or services used by another entity.
-
D.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
E.
softwareFor
Indicates that one entity is designed, intended, or used to operate on, support, or be compatible with another entity as software.
- F. None of above. chosen
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. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:01 p.m.