Triple
T29628013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western herbalism |
E755196
|
entity |
| Predicate | commonlyUsesHerb |
P41593
|
FINISHED |
| Object | chamomile |
—
|
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: chamomile | Statement: [Western herbalism, commonlyUsesHerb, chamomile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyUsesHerb Context triple: [Western herbalism, commonlyUsesHerb, chamomile]
-
A.
includesHerb
chosen
Indicates that one entity contains or incorporates a herb as part of its composition or contents.
-
B.
medicinalUse
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
C.
partUsedMedicinally
Indicates that a specific part of an entity (such as a plant or organism) is used for medicinal purposes.
-
D.
isMedicinalPlant
Indicates that a plant is used for medicinal purposes, such as treating, preventing, or alleviating health conditions.
-
E.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:39 p.m.