Triple
T3726822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bj league |
E81768
|
entity |
| Predicate | fanEngagementMethods |
P34550
|
FINISHED |
| Object | cheerleading squads |
—
|
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: cheerleading squads | Statement: [bj league, fanEngagementMethods, cheerleading squads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanEngagementMethods Context triple: [bj league, fanEngagementMethods, cheerleading squads]
-
A.
fanBaseInteraction
chosen
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
B.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
C.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
D.
hasFanCommunity
Indicates that an entity is associated with a group of fans who actively follow, support, or engage around it.
-
E.
agingMethod
Indicates the process or technique by which something (typically a product or material) is matured, aged, or allowed to develop its characteristics over time.
- 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf7a6908190bd0c3bb5c55ab9ee |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0452f5081909c79e114a86cce8c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.