Triple
T4235288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apoidea |
E94677
|
entity |
| Predicate | pollenTransportStructure |
P54841
|
FINISHED |
| Object | scopa |
—
|
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: scopa | Statement: [Apoidea, pollenTransportStructure, scopa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pollenTransportStructure Context triple: [Apoidea, pollenTransportStructure, scopa]
-
A.
pollenType
Indicates the specific kind or category of pollen associated with an entity.
-
B.
pollinatedBy
Indicates that an entity receives pollen from another entity, which acts as the pollinator enabling its fertilization or reproduction.
-
C.
pollination
Indicates the transfer of pollen from one flower’s reproductive structures to another’s, enabling fertilization and seed production.
-
D.
pollinates
Indicates that one entity transfers pollen to another, enabling or contributing to its fertilization or reproduction.
-
E.
reproductiveStructure
Indicates that one entity serves as a reproductive organ or structure of another, involved in producing or facilitating the formation of offspring or reproductive cells.
- F. None of above. chosen
Provenance (4 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e72ff588190a50c04ab975612dd |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.