Triple
T2802897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Werner Koch |
E53185
|
entity |
| Predicate | softwareTypeDeveloped |
P32488
|
FINISHED |
| Object | encryption software |
—
|
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: encryption software | Statement: [Werner Koch, softwareTypeDeveloped, encryption software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareTypeDeveloped Context triple: [Werner Koch, softwareTypeDeveloped, encryption software]
-
A.
developedWith
Indicates that something was created, built, or produced using a specified tool, technology, method, or collaborator.
-
B.
developedOn
Indicates that something was created, built, or produced using a particular platform, technology, or environment.
-
C.
softwareTypeMaintained
Indicates that an entity is responsible for maintaining or supporting a particular type of software.
-
D.
developedAs
Indicates that one entity was created, designed, or evolved specifically to function as or replace another entity.
-
E.
isDevelopedBy
chosen
Indicates that something (such as a product, project, or idea) is created, produced, or brought into existence through the work or effort of a particular developer or group of developers.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.