Triple
T21401620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PronoKal |
E527925
|
entity |
| Predicate | usesDietType |
P27925
|
FINISHED |
| Object | protein-based diet |
—
|
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: protein-based diet | Statement: [PronoKal, usesDietType, protein-based diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDietType Context triple: [PronoKal, usesDietType, protein-based diet]
-
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
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.
hasDietaryLaw
Indicates that one entity prescribes, follows, or is governed by a specific set of dietary rules or restrictions associated with another entity.
-
E.
characterizesDietAs
chosen
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
- 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_69e0b520ee3c8190abddbee7e37e834c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b1702b44819080b282c22d151c88 |
completed | April 22, 2026, 11:30 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:18 p.m.