Triple
T17375859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Die Adler |
E422435
|
entity |
| Predicate | clubSupporterCulture |
P29428
|
FINISHED |
| Object | large traveling away support |
—
|
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: large traveling away support | Statement: [Die Adler, clubSupporterCulture, large traveling away support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubSupporterCulture Context triple: [Die Adler, clubSupporterCulture, large traveling away support]
-
A.
supporterCulture
chosen
Indicates a relationship where an entity’s culture, norms, or practices are shaped by, aligned with, or strongly influenced by its supporters or fan base.
-
B.
supporterStyle
Indicates the characteristic manner or approach in which a supporter provides their support.
-
C.
supportsLeagueClub
Indicates that one entity provides backing, assistance, or endorsement to a league-affiliated club.
-
D.
fanOfSport
Indicates that a person supports, follows, or has a strong interest in a particular sport.
-
E.
teamLoyalty
Indicates a relationship where an individual consistently supports, commits to, and prioritizes the interests of a particular team over alternatives.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6c864481908507290282cc6d25 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.