Triple
T31690499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liriodendron tulipifera |
E808774
|
entity |
| Predicate | flowerAttracts |
P64055
|
FINISHED |
| Object | pollinators |
—
|
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: pollinators | Statement: [Liriodendron tulipifera, flowerAttracts, pollinators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowerAttracts Context triple: [Liriodendron tulipifera, flowerAttracts, pollinators]
-
A.
flowerUse
Indicates how a flower is used or purposed in a particular context (e.g., decorative, medicinal, culinary, or symbolic use).
-
B.
pollinates
Indicates that one entity transfers pollen to another, enabling or contributing to its fertilization or reproduction.
-
C.
flowerFunction
chosen
Indicates the biological or practical role that a flower serves, such as reproduction, attraction of pollinators, or ornamental use.
-
D.
flowerPosition
Indicates the spatial location or arrangement of a flower relative to a reference object or coordinate system.
-
E.
floweringUse
Indicates the use or application of something specifically for flowering or promoting the flowering process.
- 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_69f348ddcbc48190950cabcc25ff29b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:08 p.m.