Triple
T30388623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konqueror |
E773012
|
entity |
| Predicate | originallyUsedEngine |
P141160
|
FINISHED |
| Object | KHTML |
—
|
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: KHTML | Statement: [Konqueror, originallyUsedEngine, KHTML]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyUsedEngine Context triple: [Konqueror, originallyUsedEngine, KHTML]
-
A.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
B.
originalEngineType
chosen
Indicates the type or category of engine that an entity was initially or first equipped with.
-
C.
originalEngineModel
Indicates that one engine is the original or initial model from which another engine or engine variant is derived.
-
D.
originatesFromEngine
Indicates that something has its source, cause, or production in a particular engine.
-
E.
originOfEngine
Indicates the source or place from which an engine originates or is produced.
- 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_6a00372ff0e48190b3ed91f9bae9da6c |
completed | May 10, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_6a00359c1b8481909c1e43df9f5a789a |
completed | May 10, 2026, 7:37 a.m. |
Created at: April 29, 2026, 8:01 p.m.