Triple
T4106379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydrastidaceae |
E88459
|
entity |
| Predicate | commonNameOfNotableSpecies |
P54673
|
FINISHED |
| Object | goldenseal |
—
|
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: goldenseal | Statement: [Hydrastidaceae, commonNameOfNotableSpecies, goldenseal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonNameOfNotableSpecies Context triple: [Hydrastidaceae, commonNameOfNotableSpecies, goldenseal]
-
A.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
notableSpeciesGroup
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
-
C.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
notableSpeciesRole
Indicates that a species plays a particularly important, characteristic, or influential role in relation to another entity or context.
-
E.
notableGenus
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
- F. None of above. chosen
Provenance (4 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af03d5cce88190ad53bc6cfe10b21e |
completed | March 9, 2026, 5:31 p.m. |
Created at: March 9, 2026, 3:40 p.m.