Triple
T11515146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vibrio |
E273012
|
entity |
| Predicate | foundInFood |
P99888
|
FINISHED |
| Object | raw oysters |
—
|
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: raw oysters | Statement: [Vibrio, foundInFood, raw oysters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInFood Context triple: [Vibrio, foundInFood, raw oysters]
-
A.
foodSources
Indicates a relationship where one entity serves as a source of food or nourishment for another entity.
-
B.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
C.
foodItem
Indicates that one entity is a food item that can be eaten or used as food in relation to another entity.
-
D.
foodInteraction
Indicates an interaction or relationship involving food between entities, such as consumption, sharing, preparation, or exchange.
-
E.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by 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_69d6aae2c3748190bed2ea50dfb160dc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d86db8bf9c8190820c289e6b0c3873 |
completed | April 10, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d822ef46988190a1c360da4ee14fef |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 8, 2026, 9:36 p.m.