Triple
T9971390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Littorina littorea |
E196211
|
entity |
| Predicate | usedAsFood |
P91371
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Littorina littorea, usedAsFood, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsFood Context triple: [Littorina littorea, usedAsFood, yes]
-
A.
containsSpeciesUsedForFood
Indicates that something includes one or more species that are used as a source of food.
-
B.
culinaryUse
Indicates that one entity is used in the preparation, flavoring, or serving of food or drink for another entity.
-
C.
usesFood
Indicates that one entity employs or consumes a food item as a resource, ingredient, or means to achieve some purpose.
-
D.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
-
E.
isEatenFor
Indicates that one entity is consumed as food for the benefit, nourishment, or use of another entity.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb7b96b1c8190b9d3c1171346615a |
completed | April 2, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:48 p.m.