Triple
T21195735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banditland |
E522319
|
entity |
| Predicate | fanIdentityFor |
P77804
|
FINISHED |
| Object | Buffalo Bandits home crowd |
—
|
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: Buffalo Bandits home crowd | Statement: [Banditland, fanIdentityFor, Buffalo Bandits home crowd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanIdentityFor Context triple: [Banditland, fanIdentityFor, Buffalo Bandits home crowd]
-
A.
fanDestination
chosen
Indicates that one entity is the intended target or recipient of another entity’s enthusiasm, admiration, or fandom.
-
B.
fanOwned
Indicates that the entity is owned or controlled by fans, typically through collective or community-based ownership rather than traditional private or corporate ownership.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
E.
fanOfSport
Indicates that a person supports, follows, or has a strong interest in a particular sport.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7333bd7a0819084bbd1d6c111bc65 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.