Triple
T33346204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippeastrum |
E853800
|
entity |
| Predicate | dormancy |
P17096
|
FINISHED |
| Object | requires rest period after flowering |
—
|
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: requires rest period after flowering | Statement: [Hippeastrum, dormancy, requires rest period after flowering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dormancy Context triple: [Hippeastrum, dormancy, requires rest period after flowering]
-
A.
dormancyPeriod
Indicates the length of time an entity remains inactive or in a dormant state before resuming activity.
-
B.
seedDormancy
Indicates that a seed is in a state where it does not germinate, even under otherwise favorable environmental conditions.
-
C.
dormantAt
Indicates that an entity is in an inactive or non-operational state at a specified time or under certain conditions.
-
D.
hibernatesDuring
Indicates that an entity enters a state of hibernation throughout a specified time period or season.
-
E.
isDormant
chosen
Indicates that an entity is currently inactive or in a resting state, with its usual functions or activities temporarily suspended.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.