Triple
T4566025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto Mendelssohn Choir |
E121910
|
entity |
| Predicate | hasSubgroupType |
P38626
|
FINISHED |
| Object | chamber 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: chamber choir | Statement: [Toronto Mendelssohn Choir, hasSubgroupType, chamber choir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgroupType Context triple: [Toronto Mendelssohn Choir, hasSubgroupType, chamber choir]
-
A.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
B.
hasSubOrganizationType
chosen
Indicates that an organization is associated with or classified under a specific type or category of sub-organization.
-
C.
hasSubfieldGroup
Indicates that an entity includes or is associated with a specific subgroup of related subfields within its overall structure or domain.
-
D.
hasSubcategoryCriterion
Indicates that something is associated with a specific criterion used to define or distinguish one of its subcategories.
-
E.
hasSubsidiaryRoleInGroup
Indicates that an entity holds a secondary or supporting role within a specified group.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.