Triple
T22851319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singju |
E566361
|
entity |
| Predicate | dietaryVariation |
P68973
|
FINISHED |
| Object | vegetarian version without fermented fish |
—
|
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: vegetarian version without fermented fish | Statement: [Singju, dietaryVariation, vegetarian version without fermented fish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dietaryVariation Context triple: [Singju, dietaryVariation, vegetarian version without fermented fish]
-
A.
dietaryConsideration
Indicates a relationship where one entity specifies nutritional restrictions, preferences, or requirements that should be taken into account for another entity.
-
B.
dietVersion
chosen
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
C.
dietaryOptions
Indicates the types of diets or food-related preferences, restrictions, or choices that are applicable to or offered for an entity.
-
D.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
-
E.
dietAdvocated
Indicates that one entity promotes, recommends, or supports a particular diet for another entity or audience.
- 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:36 p.m.