Triple
T17581718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megachilidae |
E428218
|
entity |
| Predicate | pollenCarryingStructureType |
P54841
|
FINISHED |
| Object | abdominal 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: abdominal scopa | Statement: [Megachilidae, pollenCarryingStructureType, abdominal scopa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pollenCarryingStructureType Context triple: [Megachilidae, pollenCarryingStructureType, abdominal scopa]
-
A.
pollenTransportStructure
chosen
Indicates a structural feature that functions to carry or transfer pollen from one location or organism to another.
-
B.
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.
-
C.
pollenType
Indicates the specific kind or category of pollen associated with an entity.
-
D.
pollinatedBy
Indicates that an entity receives pollen from another entity, which acts as the pollinator enabling its fertilization or reproduction.
-
E.
flowerStructure
Indicates the structural characteristics or organization of a flower, such as the arrangement and form of its parts.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463ce8eb081909257be47d150aa04 |
completed | April 19, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.