Triple
T16338434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Partenopei |
E396733
|
entity |
| Predicate | associatedWithSupporterGroupType |
P80302
|
FINISHED |
| Object | ultras of S.S.C. Napoli |
—
|
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: ultras of S.S.C. Napoli | Statement: [Partenopei, associatedWithSupporterGroupType, ultras of S.S.C. Napoli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSupporterGroupType Context triple: [Partenopei, associatedWithSupporterGroupType, ultras of S.S.C. Napoli]
-
A.
supportersGroupType
chosen
Indicates the classification or category of a supporters group associated with an entity.
-
B.
hasSupporterGroup
Indicates that an entity is associated with a group of supporters that backs, promotes, or advocates for it.
-
C.
associatedWithSupporters
Indicates that an entity has a relationship or connection with individuals or groups who support or advocate for it.
-
D.
supporterType
Indicates the specific role or category of support a supporter provides in relation to another entity or activity.
-
E.
supportsGroupType
Indicates that one entity is compatible with or able to support a particular category or type of group.
- 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_69d87f26864c819088365ca381a003c2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2c4e6338081908aa03ee3dcbe5f70 |
completed | April 17, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69e226eba9b48190af6e80d3d1c2aed3 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.