Triple
T10978604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonezawa beef |
E259437
|
entity |
| Predicate | cattleType |
P47296
|
FINISHED |
| Object | wagyu |
E892772
|
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: wagyu | Statement: [Yonezawa beef, cattleType, wagyu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: wagyu Context triple: [Yonezawa beef, cattleType, wagyu]
-
A.
Wagyu beef
chosen
Wagyu beef is a highly prized Japanese beef known for its exceptional marbling, tenderness, and rich, buttery flavor.
-
B.
Awaji beef
Awaji beef is a premium, richly marbled wagyu beef from Japan’s Awaji Island, prized for its tenderness and deep flavor.
-
C.
Kobe beef
Kobe beef is a highly prized, richly marbled wagyu beef from Japan renowned for its exceptional tenderness and flavor.
-
D.
Yonezawa beef
Yonezawa beef is a highly prized wagyu brand from Yonezawa in Yamagata Prefecture, renowned in Japan for its exceptional marbling, tenderness, and rich flavor.
-
E.
Tajima beef
Tajima beef is a premium, highly marbled wagyu beef from Hyōgo Prefecture in Japan, renowned as the genetic source of famous brands like Kobe beef.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f7b874819087bf5a858905279b |
completed | April 9, 2026, 9:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d7bcea448190b09906c79de67496 |
completed | April 18, 2026, 1 a.m. |
Created at: April 8, 2026, 9:24 p.m.