Triple
T30955653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | オリックス・ブルーウェーブ |
E788668
|
entity |
| Predicate | 本拠地ドーム使用歴 |
P149674
|
FINISHED |
| Object | スカイマークスタジアムの前身球場を使用 |
—
|
LITERAL 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: スカイマークスタジアムの前身球場を使用 | Statement: [オリックス・ブルーウェーブ, 本拠地ドーム使用歴, スカイマークスタジアムの前身球場を使用]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 本拠地ドーム使用歴 Context triple: [オリックス・ブルーウェーブ, 本拠地ドーム使用歴, スカイマークスタジアムの前身球場を使用]
-
A.
usesBaseballStadium
Indicates that an entity regularly occupies or operates within a particular baseball stadium as its primary venue or facility.
-
B.
usesBallparksIn
Indicates that one entity makes use of or operates within specific ballparks located in a particular place or context.
-
C.
notableBallparkUsed
chosen
Indicates that a particular ballpark has been notably used or served as a significant venue for the referenced subject.
-
D.
hasStadiumUse
Indicates that one entity (typically a team, organization, or event) uses or is authorized to use a particular stadium for its activities or purposes.
-
E.
hasBallpark
Indicates that an entity possesses, is associated with, or includes a specific ballpark as part of its attributes or facilities.
- 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.