Triple
T24946745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiderettes |
E624203
|
entity |
| Predicate | fanInteraction |
P34550
|
FINISHED |
| Object | community events |
—
|
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: community events | Statement: [Raiderettes, fanInteraction, community events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanInteraction Context triple: [Raiderettes, fanInteraction, community events]
-
A.
fanBaseInteraction
chosen
Indicates interactions or engagements occurring between a fan base and the subject, such as communication, feedback, or participatory activities.
-
B.
fanInvolved
Indicates that a fan actively participates in or is directly involved with a particular event, activity, or interaction.
-
C.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
-
D.
fanAttraction
Indicates a relationship where one entity is strongly drawn to, admires, or is devoted to another as a fan.
-
E.
fanDiscussion
Indicates a discussion or conversation among fans about a shared interest, such as a work, person, or event they follow.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:54 a.m.