Triple
T29727499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordkurve |
E752222
|
entity |
| Predicate | typicalChants |
P5280
|
FINISHED |
| Object | support for 1. FC Nürnberg |
—
|
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: support for 1. FC Nürnberg | Statement: [Nordkurve, typicalChants, support for 1. FC Nürnberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalChants Context triple: [Nordkurve, typicalChants, support for 1. FC Nürnberg]
-
A.
chantingIs24x7
Indicates that the chanting activity occurs continuously, 24 hours a day, 7 days a week.
-
B.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
C.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
D.
relatedChantOrSong
Indicates that one chant or song is associated with, derived from, or otherwise connected to another chant or song.
-
E.
fanChant
chosen
Indicates a relationship where a group of fans collectively chant or vocalize in support of, or in response to, a person, team, or performance.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0235be932081908857bc3a77c27e7d |
completed | May 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a022c865dec81909e02b2f330e987e6 |
completed | May 11, 2026, 7:22 p.m. |
Created at: April 28, 2026, 7:40 p.m.