Triple
T28937471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrophulariaceae |
E730354
|
entity |
| Predicate | notableMemberUse |
P5773
|
FINISHED |
| Object | Digitalis used as a source of cardiac glycosides |
E518707
|
NE 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: Digitalis used as a source of cardiac glycosides | Statement: [Scrophulariaceae, notableMemberUse, Digitalis used as a source of cardiac glycosides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberUse Context triple: [Scrophulariaceae, notableMemberUse, Digitalis used as a source of cardiac glycosides]
-
A.
notableUse
chosen
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
B.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
C.
usedByNotablePerson
Indicates that something is or has been used by a person who is widely recognized or notable.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableUseEvent
Indicates an event in which something is used in a way that is significant or noteworthy, distinguishing it from ordinary or routine use.
- F. None of above.
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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a01beacf8a88190ac643a75c7a0efc4 |
completed | May 11, 2026, 11:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24ec41f83c81909ae31119f84874aa |
completed | June 7, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_6a01be152c8c8190bb19d64a683e2aae |
completed | May 11, 2026, 11:31 a.m. |
Created at: April 28, 2026, 8:33 a.m.