Triple
T27131487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McNuggets |
E681572
|
entity |
| Predicate | hasNutritionalConcern |
P180851
|
FINISHED |
| Object | high calorie content |
—
|
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: high calorie content | Statement: [McNuggets, hasNutritionalConcern, high calorie content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNutritionalConcern Context triple: [McNuggets, hasNutritionalConcern, high calorie content]
-
A.
hasNutrientContent
Indicates that one entity contains or provides a specified amount or type of nutrient relative to another entity or standard.
-
B.
hasNutrientStatus
Indicates that an entity possesses a particular nutritional condition or level, such as being deficient, sufficient, or excessive in specific nutrients.
-
C.
dietaryConsideration
Indicates a relationship where one entity specifies nutritional restrictions, preferences, or requirements that should be taken into account for another entity.
-
D.
nutritionalRequirement
Indicates that one entity has a need for certain nutrients or dietary conditions that must be met by another entity or resource.
-
E.
nutritionType
Indicates the specific category or kind of nutritional characteristic or value associated with an 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_69f75788d40c819083bf2567b3091585 |
completed | May 3, 2026, 2:11 p.m. |
Created at: April 27, 2026, 9:04 a.m.