Triple
T29366522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Club Irapuato |
E744733
|
entity |
| Predicate | supporterCultureFeature |
P29428
|
FINISHED |
| Object | strong local identity |
—
|
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: strong local identity | Statement: [Club Irapuato, supporterCultureFeature, strong local identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supporterCultureFeature Context triple: [Club Irapuato, supporterCultureFeature, strong local identity]
-
A.
supporterCulture
chosen
Indicates a relationship where an entity’s culture, norms, or practices are shaped by, aligned with, or strongly influenced by its supporters or fan base.
-
B.
supporterCultureElement
Indicates that a supporter endorses, promotes, or is associated with a particular cultural element.
-
C.
supporterFeatures
Indicates that one entity provides supporting characteristics, capabilities, or functionalities that enhance or enable another entity.
-
D.
shareSportsCulture
Indicates that two or more entities participate in or identify with the same sports-related traditions, values, or practices.
-
E.
supporterStyle
Indicates the characteristic manner or approach in which a supporter provides their support.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a0326d40cb88190802f61fa832f8ca8 |
completed | May 12, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_6a03268b4f9c8190b3e135b37ed373c3 |
completed | May 12, 2026, 1:09 p.m. |
Created at: April 28, 2026, 2:23 p.m.