Triple
T31156178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | オリックス・バファローズ |
E794213
|
entity |
| Predicate | プロスポーツ種別 |
P1080
|
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.
professionalSports
Indicates that the entities are connected through participation in or association with professional-level sports activities or organizations.
-
B.
traditionalSport
Indicates that an entity is a sport practiced within a culture or community that has been passed down over generations and is recognized as part of traditional or heritage activities.
-
C.
primarySport
chosen
Indicates the main sport with which an entity (such as a person, team, or organization) is most closely associated or primarily involved.
-
D.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
E.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.