Triple
T10171567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HP 902 ink series |
E235342
|
entity |
| Predicate | hasYieldOption |
P50557
|
FINISHED |
| Object | standard yield |
—
|
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: standard yield | Statement: [HP 902 ink series, hasYieldOption, standard yield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYieldOption Context triple: [HP 902 ink series, hasYieldOption, standard yield]
-
A.
hasYield
Indicates that one entity produces, returns, or generates a measurable output, result, or profit for another entity or context.
-
B.
providesOption
chosen
Indicates that one entity makes a particular choice, alternative, or configuration available to another entity.
-
C.
AbleYield
Indicates that an entity has the capability to produce, generate, or provide a specified result, output, or resource.
-
D.
optionedBy
Indicates that the rights to develop, produce, or exploit something (such as a work, property, or asset) have been contractually secured by a particular party.
-
E.
hasOptionsListed
Indicates that one entity presents or enumerates a set of selectable options associated with another entity or context.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9e4e0c819097dceb7bf7757948 |
completed | April 2, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:10 p.m.