Triple
T10742513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gol Sud |
E253361
|
entity |
| Predicate | fanGroupType |
P80302
|
FINISHED |
| Object | hardcore supporters section |
—
|
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: hardcore supporters section | Statement: [Gol Sud, fanGroupType, hardcore supporters section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanGroupType Context triple: [Gol Sud, fanGroupType, hardcore supporters section]
-
A.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
B.
fanDestination
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
C.
supportersGroupType
chosen
Indicates the classification or category of a supporters group associated with an entity.
-
D.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
E.
fanTerm
Indicates that one entity is a term, label, or expression used by fans to refer to or describe another entity.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710456ec88190ad8aff8804d13aa9 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.