Triple

T35543427
Position Surface form Disambiguated ID Type / Status
Subject Red Beans and Rice E1027126 entity
Predicate traditionallyEatenOn P199917 FINISHED
Object Monday NE NERFINISHED

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: Monday | Statement: [Red Beans and Rice, traditionallyEatenOn, Monday]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallyEatenOn
Context triple: [Red Beans and Rice, traditionallyEatenOn, Monday]
  • A. holidayFood
    Indicates that something is a type of food traditionally associated with or consumed during a holiday or festive occasion.
  • B. coFeastDayWith
    Indicates that two or more entities share the same feast day or are commemorated liturgically on the same calendar date.
  • C. isCelebratedIn
    Indicates that an event, person, or occasion is honored, observed, or commemorated within a particular place, time, or context.
  • D. isCelebratedWith
    Indicates that an event, occasion, or person is marked or honored using a particular method, activity, or accompanying element (e.g., a party, ritual, or object).
  • E. eatenOnOccasion
    Indicates that one entity is consumed or eaten by another only at certain times or under specific circumstances, rather than regularly or habitually.
  • 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_69f76e008ba08190927acd8e5e0344c8 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff63e6b61081909c648bf0ff279481 completed May 9, 2026, 4:42 p.m.
PD Predicate disambiguation batch_69ff6381867881908ae0545df4b71df5 completed May 9, 2026, 4:40 p.m.
PDg Predicate description generation batch_69ff63e5c35081908f69ac44e12b8f52 completed May 9, 2026, 4:42 p.m.
Created at: May 3, 2026, 4:04 p.m.