Triple
T33205976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St John’s wort |
E850014
|
entity |
| Predicate | hasActiveConstituent |
P82021
|
FINISHED |
| Object | hypericin |
—
|
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: hypericin | Statement: [St John’s wort, hasActiveConstituent, hypericin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActiveConstituent Context triple: [St John’s wort, hasActiveConstituent, hypericin]
-
A.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
B.
hasPrimaryConstituent
chosen
Indicates that one entity serves as the main or principal component, ingredient, or element of another entity.
-
C.
hasActiveSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or actively present.
-
D.
hasExtantMembers
Indicates that the referenced group, category, or lineage currently has living or existing members.
-
E.
hasNonConstituentMember
Indicates that an entity includes a member or component that is not formally recognized as a constituent part of it.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:30 a.m.