Triple
T23752721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lannea microcarpa |
E587013
|
entity |
| Predicate | partUsedInMedicine |
P147501
|
FINISHED |
| Object | bark |
—
|
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: bark | Statement: [Lannea microcarpa, partUsedInMedicine, bark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partUsedInMedicine Context triple: [Lannea microcarpa, partUsedInMedicine, bark]
-
A.
partUsedMedicinally
chosen
Indicates that a specific part of an entity (such as a plant or organism) is used for medicinal purposes.
-
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.
diseaseUsed
Indicates that a particular disease is employed or utilized as a tool, model, or condition within a given context or process.
-
D.
drugProduced
Indicates that a particular drug is manufactured or generated by a specified producer or source.
-
E.
knownForTreatmentOf
Indicates that an entity is recognized or notable for providing treatment or medical care for a particular condition, disease, or type of patient.
- 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc3a06c81908e8a6e1f531c73bc |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.