Triple
T34208461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umbellularia californica |
E877580
|
entity |
| Predicate | leafEffectOnHumans |
P43904
|
FINISHED |
| Object | can cause headaches in some people |
—
|
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: can cause headaches in some people | Statement: [Umbellularia californica, leafEffectOnHumans, can cause headaches in some people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leafEffectOnHumans Context triple: [Umbellularia californica, leafEffectOnHumans, can cause headaches in some people]
-
A.
impactOnHumans
chosen
Indicates a relationship where something produces an effect, influence, or consequence on humans.
-
B.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
C.
humanImpactLevel
Indicates the degree or extent to which human activities affect or influence a given entity, system, or environment.
-
D.
examinesHumanImpactOnNature
Indicates examining how human activities affect or alter natural environments and ecosystems.
-
E.
effectOnSystem
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71052707c8190b6b514bf87a4bc79 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.