Triple
T31870594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordtribüne |
E813585
|
entity |
| Predicate | belongsToClubCulture |
P102426
|
FINISHED |
| Object | FC St. Pauli fan culture |
—
|
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: FC St. Pauli fan culture | Statement: [Nordtribüne, belongsToClubCulture, FC St. Pauli fan culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToClubCulture Context triple: [Nordtribüne, belongsToClubCulture, FC St. Pauli fan culture]
-
A.
relatedToClub
chosen
Indicates that there is an association or connection between an entity and a club, without specifying the exact nature of that relationship.
-
B.
supportsClubIdentity
Indicates that one entity actively upholds, reinforces, or contributes to maintaining the identity, values, or character of a club.
-
C.
supportedClub
Indicates that one entity has given their backing, endorsement, or assistance to a particular club.
-
D.
associatedClubSport
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
E.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 30, 2026, 11:54 p.m.