Triple
T29727505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nordkurve |
E752222
|
entity |
| Predicate | fanGroupPresence |
P167241
|
FINISHED |
| Object | ultra groups of 1. FC Nürnberg |
—
|
NE NERFINISHED |
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: ultra groups of 1. FC Nürnberg | Statement: [Nordkurve, fanGroupPresence, ultra groups of 1. FC Nürnberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanGroupPresence Context triple: [Nordkurve, fanGroupPresence, ultra groups of 1. FC Nürnberg]
-
A.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
B.
UNPresence
Indicates the presence, involvement, or deployment of United Nations personnel, missions, or operations in relation to an entity or location.
-
C.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
D.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
E.
globalPresence
Indicates that an entity operates, is represented, or has a significant footprint across multiple countries or world regions.
- F. None of above. chosen
Provenance (4 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_69f673008bb081909623ca50205dc0a8 |
completed | May 2, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691e55cc81908d2d5c8ca4dea042 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:40 p.m.