Triple
T14074736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Mode |
E338701
|
entity |
| Predicate | associatedWithPersonaTrait |
P112715
|
FINISHED |
| Object | intensity |
—
|
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: intensity | Statement: [Beast Mode, associatedWithPersonaTrait, intensity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPersonaTrait Context triple: [Beast Mode, associatedWithPersonaTrait, intensity]
-
A.
associatedCharacterTrait
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
B.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
C.
hasSupportingCharacterTrait
Indicates that a supporting character possesses a particular trait, quality, or characteristic.
-
D.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
-
E.
associatedWithCharacterRole
Indicates that one entity has a connection or linkage to a specific character role played or held by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.