Triple
T11172175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wolverine |
E264300
|
entity |
| Predicate | featuresCharacter |
P626
|
FINISHED |
| Object | Yukio |
E260643
|
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: Yukio | Statement: [The Wolverine, featuresCharacter, Yukio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yukio Context triple: [The Wolverine, featuresCharacter, Yukio]
-
A.
Yukio
chosen
Yukio is a Japanese given name commonly used for males and borne by several notable figures in politics, arts, and entertainment.
-
B.
Yasu
Yasu is a Japanese city located in Shiga Prefecture, known for its blend of residential areas, local industry, and proximity to Lake Biwa.
-
C.
Takaishi
Takaishi is a city in Osaka Prefecture, Japan, known as a small industrial and residential hub within the Osaka metropolitan area.
-
D.
Sumio
Sumio is a Japanese physicist best known for his pioneering discovery and characterization of carbon nanotubes.
-
E.
Takayoshi
Takayoshi is a Japanese given name notably borne by Kido Takayoshi, a key samurai and statesman of the Meiji Restoration.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e89660208190b1d9e91529f5d246 |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a52daf1c81909c586e470a998073 |
completed | May 3, 2026, 1:30 a.m. |
Created at: April 8, 2026, 9:29 p.m.