Triple
T32489541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yokohama derby |
E830341
|
entity |
| Predicate | languageOfFanChants |
P3778
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Yokohama derby, languageOfFanChants, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfFanChants Context triple: [Yokohama derby, languageOfFanChants, Japanese]
-
A.
languageOfFanbase
chosen
Indicates the primary language or languages commonly used by a fanbase in its communication and expression.
-
B.
languageOfClubHeritage
Indicates the language traditionally associated with or used to represent a club’s cultural or historical heritage.
-
C.
languageOfTeamCountry
Indicates that a particular language is the official or primary language used in the country to which a given team belongs.
-
D.
languageOfYells
Indicates a relationship where a particular language is used as the medium or form of someone’s yelling or shouted expressions.
-
E.
hasFanChantPotential
Indicates that something (such as a song, phrase, or performance element) is well-suited to be adopted and enthusiastically chanted by a crowd or fanbase.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: May 1, 2026, 12:59 a.m.