Triple
T12660117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobusuke |
E302396
|
entity |
| Predicate | hasNameComponent |
P24447
|
FINISHED |
| Object | Nobu |
E733377
|
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: Nobu | Statement: [Nobusuke, hasNameComponent, Nobu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nobu Context triple: [Nobusuke, hasNameComponent, Nobu]
-
A.
Nobu
chosen
Nobu is a common Japanese given name and name element that can appear in various masculine and unisex names.
-
B.
Kenji
Kenji is a common Japanese masculine given name used by various notable individuals across fields such as music, literature, and sports.
-
C.
Nobu restaurants
Nobu restaurants are a globally renowned luxury dining chain known for their innovative Japanese-Peruvian cuisine and stylish, high-end ambiance.
-
D.
Masataka
Masataka is a Japanese given name commonly used for males.
-
E.
Jiro
Jiro is a masculine Japanese given name commonly associated with notable figures in Japanese culture, including engineers, artists, and fictional characters.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f66885e44c8190a650301b0e86d0f4 |
completed | May 2, 2026, 9:11 p.m. |
Created at: April 9, 2026, 5:19 p.m.