Triple
T9216033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynara |
E221242
|
entity |
| Predicate | containsSpeciesUsedInTraditionalMedicine |
P40129
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cynara, containsSpeciesUsedInTraditionalMedicine, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsSpeciesUsedInTraditionalMedicine Context triple: [Cynara, containsSpeciesUsedInTraditionalMedicine, true]
-
A.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
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.
containsSpeciesUsedAs
chosen
Indicates that something includes, as part of its composition or content, a particular species that is used for a specified purpose.
-
D.
traditionalUseDomain
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda096358819096d4e790da057512 |
completed | April 1, 2026, 8:40 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.