Triple
T23488164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peganum |
E570596
|
entity |
| Predicate | hasCommonUse |
P8225
|
FINISHED |
| Object | psychoactive seeds |
—
|
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: psychoactive seeds | Statement: [Peganum, hasCommonUse, psychoactive seeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonUse Context triple: [Peganum, hasCommonUse, psychoactive seeds]
-
A.
hasPopularUse
Indicates that something is widely used, accepted, or favored by a large number of people or within a broad context.
-
B.
isSometimesUsedFor
Indicates that something serves a particular purpose or function on some occasions, but not consistently or exclusively.
-
C.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
D.
hasHumanUse
chosen
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
-
E.
hasCommonAcronymUsage
Indicates that two terms share the same commonly used acronym in practice.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7d9cc08819084c532b069f867ee |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.