Triple
T14074730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Mode |
E338701
|
entity |
| Predicate | mediaNicknameCategory |
P78059
|
FINISHED |
| Object | sports nickname |
—
|
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: sports nickname | Statement: [Beast Mode, mediaNicknameCategory, sports nickname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaNicknameCategory Context triple: [Beast Mode, mediaNicknameCategory, sports nickname]
-
A.
mediaNicknameGivenBy
Indicates that a particular nickname was assigned to an entity by media organizations or outlets.
-
B.
mediaNicknameOrigin
Indicates that a media-related nickname originates from, or is derived based on, a particular source or context.
-
C.
nicknameCategory
chosen
Indicates that one entity is a nickname and the other entity is the category or type that this nickname belongs to.
-
D.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
-
E.
mediaProfile
Indicates a relationship where a media-related profile or account is associated with an entity, typically representing its presence or identity in media contexts.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5bc49881909012b66fa451f495 |
completed | April 14, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.