Triple
T37932715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quark, Inc. |
E946259
|
entity |
| Predicate | hasSupportOffering |
P57109
|
FINISHED |
| Object | technical support for QuarkXPress |
—
|
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: technical support for QuarkXPress | Statement: [Quark, Inc., hasSupportOffering, technical support for QuarkXPress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSupportOffering Context triple: [Quark, Inc., hasSupportOffering, technical support for QuarkXPress]
-
A.
hasOffering
chosen
Indicates that one entity provides, presents, or makes available an offering (such as a product, service, or item) to another entity or context.
-
B.
isOfferedBy
Indicates that a service, product, or opportunity is provided or made available by a particular entity.
-
C.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
D.
hasSupportService
Indicates that one entity provides or is associated with a support-related service for another entity.
-
E.
hasSupportCategory
Indicates that an entity is associated with a particular type or category of support it receives or provides.
- 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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00708ab11081909641d245c4282aa0 |
completed | May 10, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_6a00703daa0081908903ce3a28084d35 |
completed | May 10, 2026, 11:47 a.m. |
Created at: May 3, 2026, 4:20 p.m.