Triple
T620778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespidae |
E14506
|
entity |
| Predicate | dietLarvae |
P15764
|
FINISHED |
| Object | mostly animal prey provided by adults |
—
|
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: mostly animal prey provided by adults | Statement: [Vespidae, dietLarvae, mostly animal prey provided by adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietLarvae Context triple: [Vespidae, dietLarvae, mostly animal prey provided by adults]
-
A.
diet
Indicates that an entity regularly consumes a particular type or range of food as its primary source of nutrition.
-
B.
hasLarvalFeature
Indicates that an entity possesses a characteristic or trait specifically associated with its larval developmental stage.
-
C.
feedingType
chosen
Indicates the manner or method by which one entity provides nourishment or food to another.
-
D.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
E.
pillar
Indicates that one entity serves as a fundamental support or central, stabilizing element for another entity or system.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e3e5d80819096e72e11b533f931 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.