Triple
T20123134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shotwell |
E490661
|
entity |
| Predicate | usesDistributionMethod |
P1486
|
FINISHED |
| Object | DIY distribution |
—
|
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: DIY distribution | Statement: [Shotwell, usesDistributionMethod, DIY distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDistributionMethod Context triple: [Shotwell, usesDistributionMethod, DIY distribution]
-
A.
usedByDistribution
Indicates that something (such as a resource, component, or artifact) is utilized or consumed by a particular distribution.
-
B.
distributionMethod
chosen
Indicates the means or channel through which something (such as a product, resource, or information) is delivered or made available to recipients.
-
C.
allowsDistribution
Indicates that one entity grants permission for another entity to distribute or disseminate something (e.g., content, products, or data).
-
D.
handlesDistributionOf
Indicates that one entity is responsible for managing or overseeing the distribution or delivery of another entity.
-
E.
hasDistributionType
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6674054188190a15d55a73e86d143 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.