Triple
T3992961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keemun black tea |
E87033
|
entity |
| Predicate | usedInBlend |
P39014
|
FINISHED |
| Object | English breakfast tea |
—
|
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: English breakfast tea | Statement: [Keemun black tea, usedInBlend, English breakfast tea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInBlend Context triple: [Keemun black tea, usedInBlend, English breakfast tea]
-
A.
usedInVariant
chosen
Indicates that something (such as a component, feature, or element) is utilized or included within a particular variant or version of a larger entity.
-
B.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.