Triple
T23027203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toxicodendron pubescens |
E573350
|
entity |
| Predicate | seasonalColor |
P10587
|
FINISHED |
| Object | leaves turn red or orange in autumn |
—
|
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: leaves turn red or orange in autumn | Statement: [Toxicodendron pubescens, seasonalColor, leaves turn red or orange in autumn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonalColor Context triple: [Toxicodendron pubescens, seasonalColor, leaves turn red or orange in autumn]
-
A.
foliageSeasonalColor
chosen
Indicates the characteristic color that a plant’s foliage takes on during a particular season.
-
B.
hasSeasonalHighlight
Indicates that something features a notable or emphasized aspect during a particular season or time of year.
-
C.
colorInSummer
Indicates that an entity has a particular color specifically during the summer season.
-
D.
hasSeasonalNature
Indicates that something exhibits characteristics, behavior, or occurrence patterns that vary according to specific seasons or times of the year.
-
E.
hasSeasonalCollections
Indicates that an entity offers or maintains collections that vary according to specific seasons or times of year.
- 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.