Triple

T8623005
Position Surface form Disambiguated ID Type / Status
Subject Pelamushi E204212 entity
Predicate traditionalPreparationMethod P74140 FINISHED
Object boiled 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: boiled | Statement: [Pelamushi, traditionalPreparationMethod, boiled]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalPreparationMethod
Context triple: [Pelamushi, traditionalPreparationMethod, boiled]
  • A. traditionalPreparation
    Indicates that something is prepared or made using customary, long-established methods or techniques associated with a particular culture or practice.
  • B. traditionalProductionMethod chosen
    Indicates that something is created or carried out using long-established, customary techniques rather than modern or industrial methods.
  • C. typicalPreparation
    Indicates the usual or standard way in which something is prepared or made.
  • D. traditionalCuisine
    Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
  • E. traditionalDish
    Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
  • 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_69ca834a4ea0819094970dceb9e389f3 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5730309081909a9a0256c9bf5f8f completed March 31, 2026, 11:22 p.m.
PD Predicate disambiguation batch_69cc455906f8819082edd79cb4a1cf28 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:26 p.m.