Triple
T31870597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordtribüne |
E813585
|
entity |
| Predicate | fanGroupActivity |
P167241
|
FINISHED |
| Object | drum and capo-led chants |
—
|
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: drum and capo-led chants | Statement: [Nordtribüne, fanGroupActivity, drum and capo-led chants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanGroupActivity Context triple: [Nordtribüne, fanGroupActivity, drum and capo-led chants]
-
A.
fanGroupPresence
chosen
Indicates that a fan group is present or represented in a particular context, location, or event.
-
B.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
C.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
D.
fanAppeal
Indicates that something has qualities or characteristics that attract, engage, or strongly appeal to fans.
-
E.
fanBaseInteraction
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
- 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_69f6b09bc8bc81909ca5fb69d9628355 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:54 p.m.