Triple
T23027174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toxicodendron pubescens |
E573350
|
entity |
| Predicate | hasSap |
P66870
|
FINISHED |
| Object | urushiol-containing sap |
—
|
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: urushiol-containing sap | Statement: [Toxicodendron pubescens, hasSap, urushiol-containing sap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSap Context triple: [Toxicodendron pubescens, hasSap, urushiol-containing sap]
-
A.
sapUse
Indicates that one entity uses or applies sap (such as plant resin or a sap-based substance) in relation to another entity.
-
B.
sapContains
chosen
Indicates that one entity spatially or logically contains another as a part, component, or subset within its bounds.
-
C.
sap
Indicates the act of gradually weakening, draining, or undermining the strength, energy, or effectiveness of someone or something.
-
D.
hasCP
Indicates that an entity possesses, is associated with, or is characterized by a specific CP (such as a control point, contact person, or configuration parameter), depending on the domain context.
-
E.
sapType
Indicates the specific category or classification of SAP-related type assigned to an entity within a system or data model.
- 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_69e245b821008190b0e09cb02092aae1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1847e48c48190894525c354663dd2 |
completed | April 29, 2026, 4:09 a.m. |
| PD | Predicate disambiguation | batch_69ef3ba004a48190885aece88efd1f52 |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:52 p.m.