Triple
T30388148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KService |
E773001
|
entity |
| Predicate | frameworkTier |
P113801
|
FINISHED |
| Object | Tier 3 KDE Framework |
—
|
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: Tier 3 KDE Framework | Statement: [KService, frameworkTier, Tier 3 KDE Framework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frameworkTier Context triple: [KService, frameworkTier, Tier 3 KDE Framework]
-
A.
frameworkLevel
chosen
Indicates the hierarchical or maturity level assigned to a particular framework within a defined system or context.
-
B.
frameworkLayer
Indicates a relationship where one framework is organized within, built upon, or conceptually assigned to a particular architectural or conceptual layer.
-
C.
frameworkName
Indicates that a specific framework is identified by the given name.
-
D.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by another entity.
-
E.
architectureLevel
Indicates the relative layer or tier an entity occupies within an architectural structure or system design.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f685991b0c8190bc7ac8af9c65a010 |
completed | May 2, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.