Triple

T25606299
Position Surface form Disambiguated ID Type / Status
Subject Asahi Group Holdings E641922 entity
Predicate hasSubsidiary P254 FINISHED
Object Asahi Beer USA
Asahi Beer USA is the American subsidiary responsible for importing, marketing, and distributing Asahi Group Holdings’ beer brands in the United States.
 E1690091 NE 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: Asahi Beer USA | Statement: [Asahi Group Holdings, hasSubsidiary, Asahi Beer USA]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Asahi Beer USA
Triple: [Asahi Group Holdings, hasSubsidiary, Asahi Beer USA]
Generated description
Asahi Beer USA is the American subsidiary responsible for importing, marketing, and distributing Asahi Group Holdings’ beer brands in the United States.

Provenance (5 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_69e75dc6ccf081908d49578fd36a76d5 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f9aa9b6881909fd56b8a85534062 completed May 2, 2026, 1:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10c13c7680819085aa0854bea369e5 completed May 22, 2026, 8:49 p.m.
NEDg Description generation batch_6a10c1db351c819082d9d7ff8c9f130b completed May 22, 2026, 8:51 p.m.
NED2 Entity disambiguation (via description) batch_6a10c2897e348190b1fa494f5891d742 completed May 22, 2026, 8:54 p.m.
Created at: April 21, 2026, 4:38 p.m.