Triple
T30388626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konqueror |
E773012
|
entity |
| Predicate | roleInKDE |
P3571
|
FINISHED |
| Object | original default web browser for KDE |
—
|
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: original default web browser for KDE | Statement: [Konqueror, roleInKDE, original default web browser for KDE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInKDE Context triple: [Konqueror, roleInKDE, original default web browser for KDE]
-
A.
roleInCommunity
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
B.
roleInEcosystem
chosen
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
C.
roleInKuomboka
Indicates that an entity holds a specific role or function within the context of the Kuomboka ceremony or event.
-
D.
roleInToolchain
Indicates that an entity serves a specific function or position within a larger sequence of tools or processes in a toolchain.
-
E.
roleInDocumenta
Indicates that an entity holds a specific role or function within the context of a particular document.
- 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_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
Created at: April 29, 2026, 8:01 p.m.