Triple
T15359095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Bat |
E367240
|
entity |
| Predicate | collaborationFeature |
P42125
|
FINISHED |
| Object | Ty Segall and other musicians |
—
|
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: Ty Segall and other musicians | Statement: [Broken Bat, collaborationFeature, Ty Segall and other musicians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationFeature Context triple: [Broken Bat, collaborationFeature, Ty Segall and other musicians]
-
A.
supportsCollaborationFeature
Indicates that one entity provides or enables a collaboration-related feature for another entity or within a system.
-
B.
collaborationAspect
chosen
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
E.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
- 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_69d85a1483788190ad93c2748e8af34b |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2d4934819097fc63603964217c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.