Triple
T5244471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TSV 1860 Munich |
E118423
|
entity |
| Predicate | traditionalFanBase |
P897
|
FINISHED |
| Object | working-class 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: working-class supporters | Statement: [TSV 1860 Munich, traditionalFanBase, working-class supporters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFanBase Context triple: [TSV 1860 Munich, traditionalFanBase, working-class supporters]
-
A.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
B.
fanBelief
Indicates that a fan holds a particular belief, opinion, or conviction about someone or something.
-
C.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
D.
popularSport
Indicates that a sport is widely liked, followed, or played by many people within a certain group or region.
-
E.
fanBaseRelationship
Indicates a relationship in which one party is a fan or supporter of another, typically involving admiration, following, or dedicated interest.
- 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_69bd4468aacc8190a8196f71855cdf4f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b4fa0ec8190bce3da09aa768726 |
completed | March 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69bd77c1397c8190a7fd844d7a396e54 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.