Triple
T4830925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanshin–Yomiuri rivalry |
E107941
|
entity |
| Predicate | fanBaseOfYomiuriGiants |
P897
|
FINISHED |
| Object | nationwide supporters |
—
|
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: nationwide supporters | Statement: [Hanshin–Yomiuri rivalry, fanBaseOfYomiuriGiants, nationwide supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseOfYomiuriGiants Context triple: [Hanshin–Yomiuri rivalry, fanBaseOfYomiuriGiants, nationwide supporters]
-
A.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
JapanSeriesTitle
Indicates that the given title is the name used for a series in Japan.
-
C.
NPBTeam
Indicates that an entity is a professional baseball team that competes in Japan’s Nippon Professional Baseball (NPB) league.
-
D.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
-
E.
playsJapanSeriesAgainst
Indicates that one entity participates in a Japan Series baseball matchup as an opponent against 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.