Triple
T28915909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujitsu Soccer Club |
E733362
|
entity |
| Predicate | successorLeagueClub |
P195349
|
FINISHED |
| Object | Kawasaki Frontale |
—
|
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: Kawasaki Frontale | Statement: [Fujitsu Soccer Club, successorLeagueClub, Kawasaki Frontale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLeagueClub Context triple: [Fujitsu Soccer Club, successorLeagueClub, Kawasaki Frontale]
-
A.
successorClubPlaysIn
Indicates that the club which succeeds another club participates in a specified league or competition.
-
B.
successorClubCountry
Indicates that one club is the successor of another club within the same country, typically following reformation, relocation, or legal/organizational continuity.
-
C.
successorTeamLeague
Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
-
D.
notableSuccessorClub
Indicates that one club is widely recognized as the prominent successor or continuation of another club.
-
E.
successorClubLocation
Indicates that the location specified is where the successor club of a previous sports or organizational club is based.
- F. None of above. chosen
Provenance (4 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 28, 2026, 8:14 a.m.