Triple
T16441806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culex |
E399317
|
entity |
| Predicate | femaleFeedsOn |
P122802
|
FINISHED |
| Object | human blood |
—
|
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: human blood | Statement: [Culex, femaleFeedsOn, human blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: femaleFeedsOn Context triple: [Culex, femaleFeedsOn, human blood]
-
A.
feedingHabitat
Indicates the type of environment or location where an organism typically obtains and consumes its food.
-
B.
doesNotFeedOn
Indicates that one entity does not use another entity as a source of food or nourishment.
-
C.
feedingType
Indicates the manner or method by which one entity provides nourishment or food to another.
-
D.
bearsOnBreast
Indicates that one entity is depicted or represented as being carried or displayed on the breast or chest area of another entity.
-
E.
notableFeedingBehavior
Indicates a characteristic way or pattern in which an entity typically obtains or consumes food that is considered distinctive or noteworthy.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba91dc48190bc35db60f63d36d3 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.