Triple
T12824951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoshinobu |
E306624
|
entity |
| Predicate | hasNameElement |
P3097
|
FINISHED |
| Object | yoshi |
E76860
|
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: yoshi | Statement: [Yoshinobu, hasNameElement, yoshi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: yoshi Context triple: [Yoshinobu, hasNameElement, yoshi]
-
A.
Yoshi
chosen
Yoshi is a friendly, dinosaur-like character from Nintendo’s Mario franchise, known for his long tongue, egg-throwing abilities, and frequent role as Mario’s companion and steed.
-
B.
Yoshisuke
Yoshisuke is a Japanese given name most notably borne by industrialist Yoshisuke Aikawa, founder of the Nissan zaibatsu.
-
C.
Yoshihiro
Yoshihiro is the Japanese given name of the political scientist and author Francis Fukuyama.
-
D.
Yoshi Egg
The Yoshi Egg is a distinctive white egg with green spots from the Mario video game series, commonly associated with hatching or summoning the dinosaur-like character Yoshi.
-
E.
YU
YU is the IATA airline designator assigned to EuroAtlantic Airways, a Portuguese charter and wet-lease carrier.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96edcc99c8190986cd78fe4714835 |
completed | April 10, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ed4f7388190ba989b8a79bd7c6d |
completed | May 2, 2026, 11:55 p.m. |
Created at: April 9, 2026, 5:32 p.m.