Triple
T3242771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buccos |
E67999
|
entity |
| Predicate | fanCultureElementOf |
P14308
|
FINISHED |
| Object | Pittsburgh Pirates fanbase |
—
|
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: Pittsburgh Pirates fanbase | Statement: [Buccos, fanCultureElementOf, Pittsburgh Pirates fanbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanCultureElementOf Context triple: [Buccos, fanCultureElementOf, Pittsburgh Pirates fanbase]
-
A.
fanCultureElement
chosen
Indicates a relationship where something is a notable practice, artifact, or tradition that characterizes or expresses a particular fan culture.
-
B.
fandomCulture
Indicates a relationship where one entity is associated with, shaped by, or participates in the shared practices, norms, and creative activities of a particular fan community.
-
C.
fandomFocus
Indicates that one entity is primarily centered on, dedicated to, or concerned with the fan community or fan-related aspects of another entity.
-
D.
fandomContext
Indicates that the relationship or action occurs specifically within the context of a particular fandom or fan community.
-
E.
fandomBase
Indicates that one entity serves as the primary fan community, origin, or core support base for 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_69ad858e4c708190aa31d486cfee8a6a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf17463481909447f6ab46016407 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.