Triple
T11036061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lovelight |
E260887
|
entity |
| Predicate | performerGenderMix |
P81870
|
FINISHED |
| Object | mixed-gender vocal group |
—
|
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: mixed-gender vocal group | Statement: [Lovelight, performerGenderMix, mixed-gender vocal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performerGenderMix Context triple: [Lovelight, performerGenderMix, mixed-gender vocal group]
-
A.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
hasPerformerGenderComposition
chosen
Indicates the gender makeup of the group of performers involved in an event or performance.
-
C.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e9e3fc8190802195ac9fcb8e28 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.