Triple
T17448805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colletidae |
E424855
|
entity |
| Predicate | larvalFoodProvisioning |
P125908
|
FINISHED |
| Object | mass provisioning of brood cells |
—
|
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: mass provisioning of brood cells | Statement: [Colletidae, larvalFoodProvisioning, mass provisioning of brood cells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: larvalFoodProvisioning Context triple: [Colletidae, larvalFoodProvisioning, mass provisioning of brood cells]
-
A.
hasLarvalDiet
chosen
Indicates the type of food or feeding behavior an organism relies on during its larval stage.
-
B.
larvalBehavior
Indicates the characteristic actions or responses exhibited by an organism during its larval stage.
-
C.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
D.
larvalLifestyle
Indicates the type of lifestyle or ecological mode an organism exhibits during its larval stage.
-
E.
feedingStructure
Indicates a relationship where one entity serves as the anatomical or mechanical structure used by another entity to obtain or ingest food.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4513b99908190a6b5833559856c8b |
completed | April 19, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.