Triple
T8425126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Eye |
E198962
|
entity |
| Predicate | hasPerformerGenderComposition |
P81870
|
FINISHED |
| Object | mixed-gender 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 group | Statement: [Third Eye, hasPerformerGenderComposition, mixed-gender group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerGenderComposition Context triple: [Third Eye, hasPerformerGenderComposition, mixed-gender group]
-
A.
hasPerformerGender
Indicates that an action, event, or performance is associated with the gender of the performer who carries it out.
-
B.
hasNumberOfGenders
Indicates the relationship that specifies how many distinct genders are associated with or recognized for a given entity.
-
C.
hasHostGender
Indicates that an entity has or is associated with a specific gender of its host.
-
D.
hasFemaleVocalist
Indicates that the subject entity features or includes at least one female vocalist as a performer.
-
E.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb85a2871081908a4093838fc93b5a |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d7ea348190aafbf8ca02b7b7d5 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:07 p.m.