Triple
T29200672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yame |
E740261
|
entity |
| Predicate | teaBrandOrDesignation |
P86675
|
FINISHED |
| Object | Yamecha |
—
|
NE NERFINISHED |
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: Yamecha | Statement: [Yame, teaBrandOrDesignation, Yamecha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teaBrandOrDesignation Context triple: [Yame, teaBrandOrDesignation, Yamecha]
-
A.
teaBrand
chosen
Indicates that one entity is a brand or producer associated with a particular type or product line of tea for the other entity.
-
B.
teaProduct
Indicates that something is a product related to tea, such as an item made from, flavored with, or intended for preparing or consuming tea.
-
C.
teaType
Indicates the specific variety or category of tea associated with an entity.
-
D.
teaCategory
Indicates that one item is classified as belonging to a particular category or type of tea.
-
E.
coffeeBrand
Indicates that one entity is a brand associated with the production or marketing of coffee products for the other entity.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c58d2081909091380f074097be |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:06 p.m.