Triple
T23644971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toxicodendron potaninii |
E584006
|
entity |
| Predicate | hasCommonPropertyWith |
P101792
|
FINISHED |
| Object | other Toxicodendron species |
—
|
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: other Toxicodendron species | Statement: [Toxicodendron potaninii, hasCommonPropertyWith, other Toxicodendron species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonPropertyWith Context triple: [Toxicodendron potaninii, hasCommonPropertyWith, other Toxicodendron species]
-
A.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
B.
hasCommonValue
Indicates that two or more entities share at least one identical value or attribute in common.
-
C.
hasCommonTraitWith
chosen
Indicates that two entities share at least one trait, characteristic, or property in common.
-
D.
hasCommonElement
Indicates that two sets, collections, or groups share at least one element in common.
-
E.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2847ba08190ad2427a82fada698 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.