Triple
T26394464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanfrecce Hiroshima |
E663508
|
entity |
| Predicate | formerCompanyTeam |
P15460
|
FINISHED |
| Object | Mazda SC |
—
|
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: Mazda SC | Statement: [Sanfrecce Hiroshima, formerCompanyTeam, Mazda SC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCompanyTeam Context triple: [Sanfrecce Hiroshima, formerCompanyTeam, Mazda SC]
-
A.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
B.
formerLeagueTeam
Indicates that an entity was previously a member team of a particular sports league but is no longer part of that league.
-
C.
hasFormerTeam
chosen
Indicates that an entity was previously a member of, played for, or was affiliated with a team in the past but is no longer associated with that team.
-
D.
associatedTeamName
Indicates the name of the team that is linked or connected to a given entity.
-
E.
formerTeamNameInRivalry
Indicates that a team previously had a specific name during the period of a particular rivalry.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 26, 2026, 11:28 p.m.