Triple
T29100686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yakuza |
E736632
|
entity |
| Predicate | franchiseNameChange |
P125054
|
FINISHED |
| Object | Like a Dragon (English branding) |
—
|
NE NERFINISHED |
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: Like a Dragon (English branding) | Statement: [Yakuza, franchiseNameChange, Like a Dragon (English branding)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseNameChange Context triple: [Yakuza, franchiseNameChange, Like a Dragon (English branding)]
-
A.
franchiseRenamedAs
chosen
Indicates that an existing franchise has changed its official name to a new one.
-
B.
franchiseChange
Indicates a change in the ownership, control, or branding rights of a franchise from one party to another.
-
C.
typeOfFranchiseChange
Indicates a change in the status, ownership, or structure of a franchise relationship between entities.
-
D.
franchiseName
Indicates that an entity is identified by or associated with a specific franchise’s official name.
-
E.
officialNameChangeTo
Indicates that an entity’s official name has been changed from a previous name to a new specified name.
- F. None of above.
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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 11:11 a.m.