Triple
T908575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macleaya |
E19604
|
entity |
| Predicate | potentialRisk |
P8576
|
FINISHED |
| Object | can be invasive in suitable climates |
—
|
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 be invasive in suitable climates | Statement: [Macleaya, potentialRisk, can be invasive in suitable climates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialRisk Context triple: [Macleaya, potentialRisk, can be invasive in suitable climates]
-
A.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
B.
riskFeature
chosen
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
-
C.
risk
Indicates that one entity is exposed or subject to potential harm, loss, or adverse outcome arising from another entity, action, or situation.
-
D.
riskLevel
Indicates the degree of potential harm, loss, or adverse outcome associated with a particular situation, action, or entity.
-
E.
riskIfNoncompliance
Indicates that a risk or negative consequence will occur if the specified rules, requirements, or obligations are not complied with.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b28ff5948190982c4439eadf9d87 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.