Triple
T10490933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Army Choir |
E247415
|
entity |
| Predicate | typicalEnsembleComponents |
P24652
|
FINISHED |
| Object | male choir |
—
|
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: male choir | Statement: [Red Army Choir, typicalEnsembleComponents, male choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnsembleComponents Context triple: [Red Army Choir, typicalEnsembleComponents, male choir]
-
A.
typicalEnsembleType
Indicates the usual or characteristic type of ensemble associated with or used to perform a given work, piece, or musical context.
-
B.
typeOfEnsemble
chosen
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
-
C.
associatedEnsembleOf
Indicates that one entity is linked or connected to a particular ensemble, typically as a member, contributor, or related component of that group.
-
D.
typicalTeamComposition
Indicates the usual or standard combination of roles or members that make up a team.
-
E.
typicalComponent
Indicates that one entity is a standard or representative component or part of another entity.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5097d61e08190952d4354ef1bce52 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8a30848190b33cf43f005a028e |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:23 p.m.