Triple
T30955623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | オリックス・ブルーウェーブ |
E788668
|
entity |
| Predicate | 合併後名称 |
P60916
|
FINISHED |
| Object | オリックス・バファローズ |
—
|
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: オリックス・バファローズ | Statement: [オリックス・ブルーウェーブ, 合併後名称, オリックス・バファローズ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 合併後名称 Context triple: [オリックス・ブルーウェーブ, 合併後名称, オリックス・バファローズ]
-
A.
affiliationAfterMerger
Indicates that an entity becomes affiliated with another entity as a result of a merger that occurs after a specified point in time.
-
B.
parentCompanyAfterMerger
Indicates that one company is the resulting parent company of another following a merger.
-
C.
governingBodyAtMerger
Indicates the organization or authority that served as the governing body of an entity at the time it merged with another entity.
-
D.
underwentNameChangeTo
chosen
Indicates that an entity previously known by one name has changed its name to the specified new name.
-
E.
brandMergedWith
Indicates that two previously distinct brands have combined into a single unified brand entity, typically through merger or acquisition.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:54 p.m.