Triple

T34237542
Position Surface form Disambiguated ID Type / Status
Subject Corn Flakes E878374 entity
Predicate hasNutrientFortification P46082 FINISHED
Object iron 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: iron | Statement: [Corn Flakes, hasNutrientFortification, iron]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNutrientFortification
Context triple: [Corn Flakes, hasNutrientFortification, iron]
  • 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. hasAssociatedNutrient
    Indicates that one entity is linked to or contains a specific nutrient as part of its nutritional composition or association.
  • D. involvesFortificationType
    Indicates that the relationship or action includes or is associated with a specific type of fortification (e.g., defensive structure or fortified feature).
  • E. fortifiedWith chosen
    Indicates that something has been strengthened, enhanced, or reinforced by the addition of a specified substance, feature, or element.
  • 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_69f349b22d8c819096b22df268382aa9 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fe920a437081908d5174e8cf7a53a6 completed May 9, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69fe919a9a6c8190acb4483f386e6db7 completed May 9, 2026, 1:44 a.m.
Created at: May 1, 2026, 1:56 a.m.