Triple

T17771098
Position Surface form Disambiguated ID Type / Status
Subject Sam Hayward E443638 entity
Predicate usesIngredientSourcingApproach P69263 FINISHED
Object local sourcing 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: local sourcing | Statement: [Sam Hayward, usesIngredientSourcingApproach, local sourcing]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesIngredientSourcingApproach
Context triple: [Sam Hayward, usesIngredientSourcingApproach, local sourcing]
  • A. usesIngredientSourcing
    Indicates that one entity obtains or incorporates another entity as a source of ingredients in its operations or products.
  • B. productSourcingStrategy chosen
    Indicates the approach or method by which a product is obtained or sourced, such as from suppliers, manufacturers, or other channels.
  • C. usesIngredientInfluenceFrom
    Indicates that one entity incorporates or applies the influence, properties, or effects derived from a particular ingredient in its action or outcome.
  • D. usesIngredient
    Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
  • E. allowsUseOfNonLocalIngredients
    Indicates that an entity permits the use of ingredients sourced from outside the local area.
  • 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_69d8b9edf16c8190a59ebd245d378f4f completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e485ff928481909fe32260ba57978f completed April 19, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69e3d8d8e538819084f1584426b41d5e completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:11 a.m.