Triple

T38048566
Position Surface form Disambiguated ID Type / Status
Subject Empire Brewery E949688 entity
Predicate immigrantFounderOriginCountry P100971 FINISHED
Object Germany 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: Germany | Statement: [Empire Brewery, immigrantFounderOriginCountry, Germany]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: immigrantFounderOriginCountry
Context triple: [Empire Brewery, immigrantFounderOriginCountry, Germany]
  • A. foundingMemberImmigratedFrom chosen
    Indicates that a founding member of an organization or group originally came from or immigrated from a specified place or country.
  • B. foundingMemberImmigratedTo
    Indicates that a founding member of an entity moved from their original country or region to the specified destination location.
  • C. founderNationality
    Indicates that the specified person’s country of origin or citizenship is the one associated with the founder in question.
  • D. immigratesFrom
    Indicates that an entity moves to live in a new country or region, originating from the specified source country or region.
  • E. countryOfEmigration
    Indicates the country from which a person or group has emigrated or moved away.
  • 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_69f76f000cf081908c11fb5443b392e6 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fc44c7e73c819082d4fc1900fb9632 completed May 7, 2026, 7:52 a.m.
PD Predicate disambiguation batch_69fbc8efffbc8190a139798ad1880526 completed May 6, 2026, 11:04 p.m.
Created at: May 3, 2026, 4:20 p.m.