Triple

T2717683
Position Surface form Disambiguated ID Type / Status
Subject Angostura bitters E60005 entity
Predicate regulatoryClassification P29562 FINISHED
Object non-potable bitters 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: non-potable bitters | Statement: [Angostura bitters, regulatoryClassification, non-potable bitters]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regulatoryClassification
Context triple: [Angostura bitters, regulatoryClassification, non-potable bitters]
  • A. regulatoryType
    Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
  • B. governingClassification chosen
    Indicates the classification system or category framework that determines how an entity is organized, labeled, or regulated.
  • C. regulationStatus
    Indicates the regulatory condition or compliance state that applies to an entity under relevant rules or laws.
  • D. areClassifiedBy
    Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
  • E. regulatoryStandard
    Indicates that one entity serves as an official rule, guideline, or benchmark that governs, constrains, or evaluates the behavior, quality, or performance of another entity.
  • 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_69ab4b746d248190958e052045c09255 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abdaad577c8190819d3c641c2406f4 completed March 7, 2026, 7:58 a.m.
PD Predicate disambiguation batch_69abd8240920819087a812d816a55edb completed March 7, 2026, 7:47 a.m.
Created at: March 6, 2026, 9:55 p.m.