Triple
T19296323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western League |
E482570
|
entity |
| Predicate | teamAffiliationSystem |
P13616
|
FINISHED |
| Object | one-to-one with NPB parent clubs |
—
|
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: one-to-one with NPB parent clubs | Statement: [Western League, teamAffiliationSystem, one-to-one with NPB parent clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAffiliationSystem Context triple: [Western League, teamAffiliationSystem, one-to-one with NPB parent clubs]
-
A.
teamAffiliationStructure
chosen
Indicates the organizational relationship that defines how a team is structured, including its internal roles, hierarchy, and affiliations.
-
B.
playerAffiliation
Indicates the organization, team, or group with which a player is formally associated or aligned.
-
C.
leagueAffiliationOfTeam
Indicates that a sports team is affiliated with, or competes within, a particular league.
-
D.
leagueAffiliationManaged
Indicates that one entity manages, oversees, or administers the league affiliation of another entity.
-
E.
teamAffiliationInStory
Indicates that, within the context of a particular story, one entity is affiliated with or belongs to a specific team.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc85e8988190a98bc291121f0153 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.