Triple
T19916498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trop50 |
E478677
|
entity |
| Predicate | associatedWithDietType |
P135801
|
FINISHED |
| Object | calorie-conscious 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: calorie-conscious diet | Statement: [Trop50, associatedWithDietType, calorie-conscious diet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDietType Context triple: [Trop50, associatedWithDietType, calorie-conscious diet]
-
A.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an entity.
-
B.
characterizesDietAs
Indicates that one entity describes, defines, or assigns the type or nature of another entity’s diet.
-
C.
dietVersion
Indicates that one diet is a specific version, variant, or iteration of another diet.
-
D.
dietaryConsideration
chosen
Indicates a relationship where one entity specifies nutritional restrictions, preferences, or requirements that should be taken into account for another entity.
-
E.
membersDiet
Indicates the type of diet that the members of a group, organization, or category typically follow or are characterized by.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65994f4608190b79771ddea1040f5 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.