Triple
T4052404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nomadinae |
E84613
|
entity |
| Predicate | hostGroup |
P2901
|
FINISHED |
| Object | solitary 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: solitary bees | Statement: [Nomadinae, hostGroup, solitary bees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostGroup Context triple: [Nomadinae, hostGroup, solitary bees]
-
A.
hostConfederation
Indicates that an entity serves as the organizing or hosting confederation for a particular event, competition, or activity.
-
B.
hostAssociation
Indicates a relationship in which one entity serves as the host or primary supporting environment for another entity.
-
C.
hostRange
chosen
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
-
D.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
-
E.
hostNOC
Indicates that one entity operates as the Network Operations Center (NOC) responsible for monitoring, managing, or supporting another entity’s network or services.
- 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.