Triple
T18757600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paeoniaceae |
E458689
|
entity |
| Predicate | hasSpeciesUsedIn |
P40129
|
FINISHED |
| Object | traditional medicine |
—
|
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: traditional medicine | Statement: [Paeoniaceae, hasSpeciesUsedIn, traditional medicine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciesUsedIn Context triple: [Paeoniaceae, hasSpeciesUsedIn, traditional medicine]
-
A.
containsSpeciesUsedAs
chosen
Indicates that something includes, as part of its composition or content, a particular species that is used for a specified purpose.
-
B.
usedBySpecies
Indicates that something (such as an object, resource, or method) is utilized or employed by a particular species.
-
C.
hasSpeciesRole
Indicates that an entity plays a specific functional or categorical role within a particular species.
-
D.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f359e48190a64b7360dd3bed3a |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.