Triple
T24039043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mike Banks |
E595319
|
entity |
| Predicate | collectiveTypeAssociated |
P99297
|
FINISHED |
| Object | music collective |
—
|
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: music collective | Statement: [Mike Banks, collectiveTypeAssociated, music collective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectiveTypeAssociated Context triple: [Mike Banks, collectiveTypeAssociated, music collective]
-
A.
collectiveOrganizationType
chosen
Indicates the specific kind or category of collective organization that an entity belongs to or is classified as.
-
B.
associatedCollectiveRole
Indicates that an entity is linked to a role or function held within a collective, group, or organization.
-
C.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
associatedProducerCollective
Indicates a relationship where an entity is linked to, or works in connection with, a specific producer collective.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d7a51c8190b108a4f862843209 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:57 p.m.