Triple
T8749900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartsease |
E207930
|
entity |
| Predicate | traditionalUseFor |
P40313
|
FINISHED |
| Object | skin conditions |
—
|
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: skin conditions | Statement: [Heartsease, traditionalUseFor, skin conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalUseFor Context triple: [Heartsease, traditionalUseFor, skin conditions]
-
A.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
B.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
C.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
D.
medicinalUse
chosen
Indicates that one entity is used as a treatment or remedy for a disease, condition, or health-related purpose affecting another entity.
-
E.
hasUseInTradition
Indicates that something is employed or holds a functional role within a particular cultural, religious, or historical tradition.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da5d474819084ae81d21a5089fa |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.