Triple
T20898982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piper nigrum |
E514616
|
entity |
| Predicate | processingForBlackPepper |
P35348
|
FINISHED |
| Object | fermentation and drying |
—
|
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: fermentation and drying | Statement: [Piper nigrum, processingForBlackPepper, fermentation and drying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processingForBlackPepper Context triple: [Piper nigrum, processingForBlackPepper, fermentation and drying]
-
A.
processingUse
chosen
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
B.
processedTo
Indicates that one entity is transformed or converted into another entity through some processing operation.
-
C.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
-
D.
typicalSpices
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
-
E.
hasSpice
Indicates that one entity contains, includes, or is characterized by a particular spice or set of spices.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8f92bd88190b59b2131ad1d9aa1 |
completed | April 21, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.