Triple
T4052367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apis |
E84612
|
entity |
| Predicate | pollinationService |
P19798
|
FINISHED |
| Object | agricultural crops |
—
|
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: agricultural crops | Statement: [Apis, pollinationService, agricultural crops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pollinationService Context triple: [Apis, pollinationService, agricultural crops]
-
A.
pollinates
chosen
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
Indicates the type of pollinator or pollination mechanism with which an organism’s flowers are evolutionarily associated.
-
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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb869c34819097ec3bebe402d37b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.