Triple
T26417916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EDM |
E664148
|
entity |
| Predicate | primaryAudienceActivity |
P8834
|
FINISHED |
| Object | dancing |
—
|
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: dancing | Statement: [EDM, primaryAudienceActivity, dancing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAudienceActivity Context triple: [EDM, primaryAudienceActivity, dancing]
-
A.
primaryEngagement
Indicates the main or most significant interaction, involvement, or relationship that an entity has with another entity or activity.
-
B.
primaryActivityPattern
Indicates the main recurring type of activity or behavior that characterizes how an entity typically operates or functions.
-
C.
secondaryAudience
Indicates that an entity is a secondary or additional intended audience or target group for another entity (such as a work, message, or product), beyond the primary audience.
-
D.
activityType
chosen
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: April 26, 2026, 11:41 p.m.