Triple
T22427649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metopium toxiferum |
E554414
|
entity |
| Predicate | sapProperty |
P148147
|
FINISHED |
| Object | highly irritating to skin |
—
|
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: highly irritating to skin | Statement: [Metopium toxiferum, sapProperty, highly irritating to skin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sapProperty Context triple: [Metopium toxiferum, sapProperty, highly irritating to skin]
-
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.
sapType
Indicates the specific category or classification of SAP-related type assigned to an entity within a system or data model.
-
C.
sap
Indicates the act of gradually weakening, draining, or undermining the strength, energy, or effectiveness of someone or something.
-
D.
sandboxProperty
Indicates that one entity has a property, setting, or attribute that is specifically defined or constrained within a sandboxed or isolated environment.
-
E.
sapContains
Indicates that one entity spatially or logically contains another as a part, component, or subset within its bounds.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2f054c819093fbe173c8a4a544 |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.