Triple
T30583325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | laphet thoke |
E778439
|
entity |
| Predicate | traditionalTeaLeafType |
P53105
|
FINISHED |
| Object | pickled green tea leaves |
—
|
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: pickled green tea leaves | Statement: [laphet thoke, traditionalTeaLeafType, pickled green tea leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalTeaLeafType Context triple: [laphet thoke, traditionalTeaLeafType, pickled green tea leaves]
-
A.
traditionalTrade
Indicates a relationship where goods or services are exchanged using long-established, customary methods rather than modern or digital trading systems.
-
B.
traditionalGreen
Indicates that something adheres to or embodies a customary or historically established form of the color green.
-
C.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
D.
traditionalHeir
Indicates that one entity is recognized as the customary or culturally designated inheritor or successor of another entity.
-
E.
teaType
chosen
Indicates the specific variety or category of tea associated with an 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 8:23 p.m.