Triple
T8395209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | western red cedar |
E198034
|
entity |
| Predicate | decayResistanceCause |
P81998
|
FINISHED |
| Object | thujaplicins and other extractives |
—
|
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: thujaplicins and other extractives | Statement: [western red cedar, decayResistanceCause, thujaplicins and other extractives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decayResistanceCause Context triple: [western red cedar, decayResistanceCause, thujaplicins and other extractives]
-
A.
damageLeadsTo
Indicates that one instance of damage causally results in or contributes to another specified outcome or condition.
-
B.
isResistant
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
-
C.
fallCause
Indicates that one event or condition causes or brings about another event of falling or decline.
-
D.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
E.
decayMode
Indicates the specific process or pathway by which an unstable entity transforms or decays into other products.
- F. None of above. chosen
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_69ca82f816bc8190ab321c07d72208c1 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81874d6c8190bbc0ac832d8a339d |
completed | March 31, 2026, 8:10 a.m. |
| PD | Predicate disambiguation | batch_69cb70d24b248190a326aa6804f942b5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:03 p.m.