Triple
T14476183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amur linden |
E358978
|
entity |
| Predicate | pollinatorAttraction |
P12305
|
FINISHED |
| Object | bees |
—
|
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: bees | Statement: [Amur linden, pollinatorAttraction, bees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pollinatorAttraction Context triple: [Amur linden, pollinatorAttraction, bees]
-
A.
pollinates
Indicates that one entity transfers pollen to another, enabling or contributing to its fertilization or reproduction.
-
B.
pollination
Indicates the transfer of pollen from one flower’s reproductive structures to another’s, enabling fertilization and seed production.
-
C.
pollinatedBy
Indicates that an entity receives pollen from another entity, which acts as the pollinator enabling its fertilization or reproduction.
-
D.
pollinationSyndrome
chosen
Indicates the type of pollinator or pollination mechanism with which an organism’s flowers are evolutionarily associated.
-
E.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91fc1fc48190842b09aa03ba79f8 |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.